Alexander Neundorf wrote:
On Sunday 13 May 2012, Stephen Kelly wrote:
Stephen Kelly wrote:
Hi there,
The topic of 'target usage requirements' has come up several times.
It's something I'd like to work further towards in CMake 2.8.9.
I have created a wiki page on the KDE wiki
On 05/17/2012 09:25 AM, Stephen Kelly wrote:
$IF($CONFIGURATION MATCHES Debug AND $LANGUAGE STREQUALS CXX)...
I'm not sure what should go in the ... part though. Some syntax to
delimit the then/else values would be needed.
I'm not sure else() and endif() are needed as additional
Brad King wrote:
On 05/17/2012 09:25 AM, Stephen Kelly wrote:
$IF($CONFIGURATION MATCHES Debug AND $LANGUAGE STREQUALS
CXX)...
I'm not sure what should go in the ... part though. Some syntax to
delimit the then/else values would be needed.
I'm not sure else() and endif() are needed
On 05/13/2012 05:50 PM, Stephen Kelly wrote:
The remaining (I think) open question regards what form the generator
expressions should take so that they can represent multiple dimensions.
Multiple dimensions will inevitably need to be combined in arbitrary
boolean expressions. I'm concerned
Stephen Kelly wrote:
Hi there,
The topic of 'target usage requirements' has come up several times. It's
something I'd like to work further towards in CMake 2.8.9.
I have created a wiki page on the KDE wiki (there for my convenience
mostly) so that we can discuss the design,
On Saturday 05 May 2012, Stephen Kelly wrote:
Alexander Neundorf wrote:
On Wednesday 02 May 2012, Stephen Kelly wrote:
Brad King wrote:
...
to mean find-if-necessary. Then arguments after Bar would be
passed to the implied find_package for version and all the other
options.
Alexander Neundorf wrote:
On Wednesday 02 May 2012, Stephen Kelly wrote:
Brad King wrote:
...
to mean find-if-necessary. Then arguments after Bar would be
passed to the implied find_package for version and all the other
options. Either Module mode or Config mode could detect whether
Clinton Stimpson wrote:
On Thursday, May 03, 2012 10:21:10 am Stephen Kelly wrote:
On 05/03/2012 06:19 PM, Ben Boeckel wrote:
On Thu, May 03, 2012 at 09:35:44 -0600, Clinton Stimpson wrote:
The include, defines, etc... can be properties on a target when when
target_use_target() is used,
Alexander Neundorf wrote:
On Thursday 03 May 2012, Stephen Kelly wrote:
Alexander Neundorf wrote:
...
So, I don't see any need for automatically invoking find_package() from
some other command. Calling find_package() is something people should
be used to, it shouldn't be hard for them.
Alexander Neundorf wrote:
On Tuesday 01 May 2012, Stephen Kelly wrote:
Stephen Kelly wrote:
This avoids the 'double booking' problem[1], which I think might be
real, so I think it's a good idea to optimize the common case, but I
won't be too disappointed if it's not acceptable.
[1]
On Thu, May 03, 2012 at 09:35:44 -0600, Clinton Stimpson wrote:
The include, defines, etc... can be properties on a target when when
target_use_target() is used, it could extract those properties and apply them
on the using target.
So we'll also need a way to define private values for these
On 05/03/2012 06:19 PM, Ben Boeckel wrote:
On Thu, May 03, 2012 at 09:35:44 -0600, Clinton Stimpson wrote:
The include, defines, etc... can be properties on a target when when
target_use_target() is used, it could extract those properties and apply them
on the using target.
So we'll also need
On Thursday, May 03, 2012 10:21:10 am Stephen Kelly wrote:
On 05/03/2012 06:19 PM, Ben Boeckel wrote:
On Thu, May 03, 2012 at 09:35:44 -0600, Clinton Stimpson wrote:
The include, defines, etc... can be properties on a target when when
target_use_target() is used, it could extract those
On Thursday 03 May 2012, Stephen Kelly wrote:
Alexander Neundorf wrote:
...
So, I don't see any need for automatically invoking find_package() from
some other command. Calling find_package() is something people should be
used to, it shouldn't be hard for them. Hiding it in some other
On Tuesday 01 May 2012, Stephen Kelly wrote:
Stephen Kelly wrote:
This avoids the 'double booking' problem[1], which I think might be real,
so I think it's a good idea to optimize the common case, but I won't be
too disappointed if it's not acceptable.
[1]
On Wednesday 02 May 2012, Stephen Kelly wrote:
Brad King wrote:
...
to mean find-if-necessary. Then arguments after Bar would be
passed to the implied find_package for version and all the other
options. Either Module mode or Config mode could detect whether
there is enough information
On Wed, May 2, 2012 at 1:18 PM, Alexander Neundorf neund...@kde.org wrote:
On Wednesday 02 May 2012, Stephen Kelly wrote:
Brad King wrote:
...
to mean find-if-necessary. Then arguments after Bar would be
passed to the implied find_package for version and all the other
options. Either
On Wed, May 2, 2012 at 2:02 PM, Alexander Neundorf neund...@kde.org wrote:
On Wednesday 02 May 2012, David Cole wrote:
On Wed, May 2, 2012 at 1:18 PM, Alexander Neundorf neund...@kde.org wrote:
On Wednesday 02 May 2012, Stephen Kelly wrote:
...
I also think the 'Foo' would be redundant. It
On Sunday 29 April 2012, Stephen Kelly wrote:
Hi there,
The topic of 'target usage requirements' has come up several times. It's
something I'd like to work further towards in CMake 2.8.9.
I have created a wiki page on the KDE wiki (there for my convenience
mostly) so that we can discuss
Brad King wrote:
On 4/29/2012 11:02 AM, Stephen Kelly wrote:
The topic of 'target usage requirements' has come up several times. It's
something I'd like to work further towards in CMake 2.8.9.
I have created a wiki page on the KDE wiki (there for my convenience
mostly) so that we can
Stephen Kelly wrote:
This avoids the 'double booking' problem[1], which I think might be real,
so I think it's a good idea to optimize the common case, but I won't be
too disappointed if it's not acceptable.
[1] http://lists.qt-project.org/pipermail/development/2011-
November/000258.html
--
On 4/29/2012 11:02 AM, Stephen Kelly wrote:
The topic of 'target usage requirements' has come up several times. It's
something I'd like to work further towards in CMake 2.8.9.
I have created a wiki page on the KDE wiki (there for my convenience mostly)
so that we can discuss the design,
Hi there,
The topic of 'target usage requirements' has come up several times. It's
something I'd like to work further towards in CMake 2.8.9.
I have created a wiki page on the KDE wiki (there for my convenience mostly)
so that we can discuss the design, implementation and implications.
23 matches
Mail list logo
