Thanks for the clarification - I have a much clearer understanding now.
--
Glenn
On 18 June 2011 14:30, Michael Hertling mhertl...@online.de wrote:
COMPILE_DEFINITIONS is used *always*, i.e. for every generator in every
configuration, and COMPILE_DEFINITIONS_CONFIG is used *additionally*
in
On 06/16/2011 11:44 PM, Glenn Coombs wrote:
On 16 June 2011 15:45, Michael Hertling mhertl...@online.de wrote:
IMO, the default should not need to be explicitly enabled but the
exception, and readability - though important - is subordinate to
functionality, but probably, this is a matter of
On 13 June 2011 02:53, Michael Hertling mhertl...@online.de wrote:
AFAIK, there's no other approach to take account of single- and multi-
config generators at the same time for this purpose, but perhaps, you
could design the loop a bit smarter:
FOREACH(i IN LISTS CMAKE_CONFIGURATION_TYPES
On 06/16/2011 03:18 PM, Glenn Coombs wrote:
On 13 June 2011 02:53, Michael Hertling mhertl...@online.de wrote:
AFAIK, there's no other approach to take account of single- and multi-
config generators at the same time for this purpose, but perhaps, you
could design the loop a bit smarter:
On 16 June 2011 15:45, Michael Hertling mhertl...@online.de wrote:
IMO, the default should not need to be explicitly enabled but the
exception, and readability - though important - is subordinate to
functionality, but probably, this is a matter of personal taste.
However, if you stick with
Glenn Coombs glenn.coo...@gmail.com
writes:
Is there a more elegant solution that I am missing ? Ideally something
like:
add_definitions(CONFIG=Debug;Release;RelWithDebInfo;MinSizeRel
-DGEN_OUTFILES)
which I know doesn't exist but I really wish it did :-)
Isn't it OK to just do something
