Brad King wrote: > On 01/04/2013 09:26 AM, Stephen Kelly wrote: >> The other uses of context->Config is in $<CONFIGURATION>, where I don't >> think the mapping should be used, and CONFIG_DEBUG, which you said >> previously should not use the mapping. >> >> http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/5398/focus=5488 > > Hmm...actually $<CONFIG_DEBUG> should evaluate to true or false based > on whether the mapped configuration was considered a debug configuration > according to the exporting project's DEBUG_CONFIGURATIONS property. > Yuck.
I agree. > Previously all export properties were generated by evaluating > each configuration of the exporting project and recording the results > at export time. Now the configuration isn't used for evaluation until > loaded by the importing project. > > One solution is to convert $<CONFIG_DEBUG> at export time to something > like $<OR:$<CONFIG:Debug1>,$<CONFIG:Debug2>,...> where Debug1;Debug2;... > are the values of the DEBUG_CONFIGURATIONS global property. Another > solution is to use the $<OR:...> approach instead of $<CONFIG_DEBUG> > altogether. I think the latter may be the best solution. > > Anyway, since $<CONFIG_DEBUG> is not part of this topic it doesn't yet > matter anyway. Yes. > The topic that adds it should be based on this topic > so it can get the config map handling. > >> If, you agree, I'll merge this to next. > > Yes, please. Thanks for splitting this out. Done, thanks, Steve. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
