<div dir="ltr">On Thu, Sep 4, 2008 at 5:37 PM, Brad King <span dir="ltr"><<a href="mailto:brad.king@kitware.com">brad.king@kitware.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Philip Lowman wrote:<br>
> Ultimately, TARGET_LINK_LIBRARIES() works just fine the way it is with<br>
> the debug/optimized keywords satisfying normal use cases. The<br>
> debug/optimized keywords are in the lexicon and they aren't going<br>
> anywhere. What is the harm in accepting a patch (if a user submitted<br>
> one) that facilitated global association of custom build configurations<br>
> with the debug/optimized keywords? I'm honestly surprised that this has<br>
> been hardcoded for as long as it has been.<br>
<br>
</div>I think the best way to define meaning of the keywords is simply to<br>
define one global property 'DEBUG_CONFIGURATIONS':<br>
<br>
set_property(GLOBAL PROPERTY DEBUG_CONFIGURATIONS Debug MyDebugConfig)<br>
<br>
The property is generic enough that it could be useful for other things<br>
later, so I'm willing to create it even though it extends the old way.<br>
The TARGET_LINK_LIBRARIES() command can use this property to define<br>
which configurations are associated with 'debug' (and all others with<br>
'optimized'). There some subtle issues with the implementation and<br>
testing of the property, so I've taken care of it.</blockquote><div><br>Thanks for adding this Brad. I like your idea of one global property for this instead of using two global variables as I originally suggested.<br>
</div></div><br>-- <br>Philip Lowman<br>
</div>