<div dir="ltr">On Tue, Aug 26, 2008 at 9:03 AM, 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><div class="Wj3C7c"><br>
</div></div>FYI, we're planning to eventually get rid of the optimized/debug link<br>
type keywords in favor of the more flexible IMPORTED target approach.<br>
We will not be accepting changes that encourage further use of these<br>
keywords.</blockquote><div><br>Brad,<br><br>I've had a look at your previous posts and I agree that IMPORTED targets look very flexible and could be used to solve the problem. <br><br>Unfortunately I think they're going to prove difficult to get people to switch to. I don't even want to speculate as to how long it will take to modify all of the find modules to support the interface before it's even possible to switch user code over to use the new feature.<br>
<br>Ultimately, TARGET_LINK_LIBRARIES() works just fine the way it is with the debug/optimized keywords satisfying normal use cases. The debug/optimized keywords are in the lexicon and they aren't going anywhere. What is the harm in accepting a patch (if a user submitted one) that facilitated global association of custom build configurations with the debug/optimized keywords? I'm honestly surprised that this has been hardcoded for as long as it has been.<br>
</div></div><br>-- <br>Philip Lowman<br>
</div>