Thanks for the clarification - I have a much clearer understanding now.<br><br>--<br>Glenn<br><br><div class="gmail_quote">On 18 June 2011 14:30, Michael Hertling <span dir="ltr"><<a href="mailto:mhertling@online.de">mhertling@online.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div></div><div class="h5"><br>
</div></div>COMPILE_DEFINITIONS is used *always*, i.e. for every generator in every<br>
configuration, and COMPILE_DEFINITIONS_<CONFIG> is used *additionally*<br>
in configuration <CONFIG>, so it can not be used to remove definitions<br>
added to COMPILE_DEFINITIONS; in fact, these properties are completely<br>
independent from each other.<br>
<div class="im"><br>
> Would that approach have worked for the multi-config generators ? Do they<br>
> use the concatenation of COMPILE_DEFINITIONS and COMPILE_DEFINITIONS_<active<br>
> config> ?<br>
<br>
</div>All generators use this concatenation, and that's the reason why you<br>
must handle "NOT CMAKE_CONFIGURATION_TYPES AND NOT CMAKE_BUILD_TYPE"<br>
separately one way or another if the GEN_OUTFILES definition is to<br>
be enabled always except for the RELEASENOOUTFILES configuration.<br>
<div><div></div><div class="h5"><br>
Regards,<br>
<br>
Michael<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br>