Well I've tried to make the problem as clear as possible but somehow it
seems it still wasn't clear enough.
In my opinion the solution which was proposed by Mathew was also pretty
clear - also not absolutly complete as he stated himself.
How should we proceed? I think Mathew understood what's my p
3-11-05 15:14, physhh . wrote:
>
>> On Tue, Nov 5, 2013 at 8:56 PM, Matthew Woehlke wrote:
>>
>>> On 2013-11-05 14:36, Alexander Neundorf wrote:
>>>
>>>> Once the cache is deleted in cmake-gui, I would expect that the
>>>> values from the command
On Tue, Nov 5, 2013 at 8:56 PM, Matthew Woehlke wrote:
> On 2013-11-05 14:36, Alexander Neundorf wrote:
>
>> I tried the following a few times in the past and noticed everytime that
>> it
>> does not work:
>> $ cd src
>> src/ $ mkdir build
>> src/ $ cd build
>> src/build/ $ cmake-gui -DSOME_VARIA
+1 for Mathews solution. To bad it's just on the developers list.
I will simply cite him:
On 2013-11-04 15:47, David Cole wrote:
>>* My question is still not answered completely:
** When should the new variable be added? On startup is not really
*>>* possible because it might be the case that
e is empty? This will not allow to overwrite the variable via
parameter but I guess that usecase is not very common?
On Mon, Nov 4, 2013 at 4:57 PM, Matthew Woehlke wrote:
> On 2013-11-02 07:58, David Cole wrote:
>
>> physhh wrote:
>>
>>> The question is: What is the ex
nal Message-
>> From: J Decker
>> To: physhh .
>> Cc: cmake
>> Sent: Fri, Nov 1, 2013 9:51 pm
>> Subject: Re: [CMake] Forwarding parameters to cmake through cmake-gui
>>
>>
>> sorry and I should ask; after reading a bit more context;
>>
>> wh
13 at 12:45 AM, Matthew Woehlke <
matthew.woeh...@kitware.com> wrote:
> On 2013-11-01 19:39, Matthew Woehlke wrote:
>
>> On 2013-11-01 17:35, physhh . wrote:
>>
>>> I've tried to implement it in the same way as CCMake seem to do it.
>>> Because I
Current patch:
http://pastebin.com/DfGZtGQT
On Fri, Nov 1, 2013 at 10:35 PM, physhh . wrote:
> I've tried to implement it in the same way as CCMake seem to do it.
> Because I can't compare it =>
> Could somone with access to ccmake test this:
> - Start CCMake with
re
- Question: Was foo overwritten with "123"?
Thanks
On Fri, Nov 1, 2013 at 7:02 PM, Matthew Woehlke wrote:
> On 2013-11-01 11:39, physhh . wrote:
>
>> that's interesting. I'm currently at a windows only machine so i can't
>> check out ccmake but can o
Yes but not all cmake projects which I build are mine. So i would still
have to modify a CMakeLists from someone else, which is in my opinion a bad
thing.
When you have the possiblity to inject cmake stuff without modifying the
project itself you can implement a clean separation between project
dep
On Fri, Nov 1, 2013 at 4:56 PM, Bill Hoffman wrote:
> On 11/1/2013 10:47 AM, physhh . wrote:
>
>> If cmake is used directly from the command line, it's possible to pass a
>> bunch of options
>> (http://www.cmake.org/cmake/**help/v2.8.12/cmake.html#**section_Opti
e->SetArgs(this->Args);
looks to me.
Why do you think that a simple forward is not enough? ccmake seems to do it
exactly that way?
On Fri, Nov 1, 2013 at 4:12 PM, Matthew Woehlke wrote:
> On 2013-11-01 10:47, physhh . wrote:
>
>> What I'm looking for:
>> If cmak
he Fillion-Robin <
jchris.filli...@kitware.com> wrote:
> Hi Physhh,
>
> I like the idea. Instead, a gui panel (with tooltips, doc, ...) should be
> autogenerated from the option associated to the corresponding cmake
> executable.
>
> Would be happy to review changes / patch
I've already searched for a feature like this but was not able to find it.
Then i've looked up in the cmake-gui source code but couldn't find anything
related.
What I'm looking for:
If cmake is used directly from the command line, it's possible to pass a
bunch of options (
http://www.cmake.org/cma
14 matches
Mail list logo
