Would it makes sense to have cmake-gui behaving like ccmake ? After all
there are both "UI".
It would accept the same set of options:
-C = Pre-load a script to populate the cache.
-D := = Create a cmake cache entry.
-U = Remove matching entries from CMake cache.
-G
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14545
==
Reported By:Orion Poplawski
Assigned To:
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 your src/binary directory
is not set properly.
So you would agree that it makes sense to do it "on conf
On 11/04/2013 03:47 PM, David Cole wrote:
> ccmake and cmake-gui *should* behave (in *my* opinion) as follows:
> - on startup, load the CMakeCache.txt values (if there are any) from
> the previous run
> - then apply the -D arguments so that any -D arguments given on the
> command line overwrite p
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 your src/binary directory
is not set properly.
So you would agree that it makes sense to do it "on configure" but
only if the cache
is emp
On Monday, November 04, 2013 09:16:11 AM Clinton Stimpson wrote:
> On Monday, November 04, 2013 10:40:15 AM Brad King wrote:
> > On 11/04/2013 10:31 AM, Clinton Stimpson wrote:
> > > But I see 2 others new problems.
> >
> > Those are features and they work together as intended.
> >
> > > 1)
> > >
On Monday, November 04, 2013 10:40:15 AM Brad King wrote:
> On 11/04/2013 10:31 AM, Clinton Stimpson wrote:
> > But I see 2 others new problems.
>
> Those are features and they work together as intended.
>
> > 1)
> > cmake_minimum_required(VERSION 2.8)
> > add_library(foo SHARED foo.cpp)
> > add_
Brad King wrote:
> On 10/30/2013 05:27 PM, Stephen Kelly wrote:
>> Brad King wrote:
>> I want to make sure that downstream uses the same GL headers and
>> libraries as the ones used to build Qt itself. The PATHS is populated
>> with information from qmake, and I wanted to prevent cmake finding
>>
On 11/04/2013 10:31 AM, Clinton Stimpson wrote:
> But I see 2 others new problems.
Those are features and they work together as intended.
> 1)
> cmake_minimum_required(VERSION 2.8)
> add_library(foo SHARED foo.cpp)
> add_library(bar SHARED bar.cpp)
> target_link_libraries(bar foo)
> set_target_pr
On Monday, November 04, 2013 09:48:57 AM Brad King wrote:
> On 11/02/2013 07:29 AM, Brad King wrote:
> > Policy CMP0022's NEW behavior is supposed to be that the
> > link interface is exactly specified by INTERFACE_LINK_LIBRARIES.
> > Therefore in this case the plain tll signature should go
> > ahe
On 11/02/2013 07:29 AM, Brad King wrote:
> Policy CMP0022's NEW behavior is supposed to be that the
> link interface is exactly specified by INTERFACE_LINK_LIBRARIES.
> Therefore in this case the plain tll signature should go
> ahead and populate *both* INTERFACE_LINK_LIBRARIES *and*
> LINK_LIBRARI
The following issue has been SUBMITTED.
==
http://cmake.org/Bug/view.php?id=14544
==
Reported By:Mathieu Malaterre
Assigned To:
12 matches
Mail list logo
