<br><br><div class="gmail_quote">On Mon, May 7, 2012 at 12:42 PM, Stephen Kelly <span dir="ltr"><<a href="mailto:steveire@gmail.com" target="_blank">steveire@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">Robert Dailey wrote:<br>
<br>
> On Mon, May 7, 2012 at 10:37 AM, Robert Dailey<br>
> <<a href="mailto:rcdailey.lists@gmail.com">rcdailey.lists@gmail.com</a>>wrote:<br>><br>
> I just tried your workaround and it does not work. It places everything in<br>
> my preprocessor definitions field, not actually on the command line.<br>
><br>
> I'm going to desperately need configuration-aware COMPILE_FLAGS, because<br>
> in Visual Studio, I have cache variables that enable certain features,<br>
> like edit & continue, minimal rebuild, etc... features that are not<br>
> compatible with /O2 (optimizations on). Since CMake has no choice but to<br>
> enable these MSVC features in all configurations, my release builds don't<br>
> work, and the user will be required to disable these features via cache<br>
> variable every time they want to build release, which is unnecessary.<br>
><br>
> If no one has the bandwidth to take up this feature I suppose I could look<br>
> into it. Anyone have any tips on how to implement this before I dive into<br>
> the CMake code?<br>
<br>
</div></div>If I've understood you I think the solution to a super-set of your problem<br>
is already under discussion:<br>
<br>
<a href="http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/3615" target="_blank">http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/3615</a></blockquote><div><br></div><div>This looks like an interesting discussion but seems like it would be a lot of work to complete. You're really targetting this for 2.8.9? I haven't seen any input from Bill or David on this, I'd like to read what they have to say.</div>
<div><br></div>Slightly unrelated observation, but the target_use_package() description in the wiki linked to by your discussion thread doesn't make any sense to me. Also what do you mean by "porcelain API"?</div>