I got a reply on the bug tracker. It's a normal and documented behavior. http://www.cmake.org/cmake/help/v3.3/prop_tgt/COMPILE_DEFINITIONS_CONFIG.html
On Thu, Sep 17, 2015 at 10:14 AM, Carl Poirier <[email protected]> wrote: > Hi guys, > > Thanks for the information. I opened a bug ticket here > <http://www.cmake.org/Bug/view.php?id=15750>. > > Carl > > On Mon, Sep 14, 2015 at 4:33 PM, Hendrik Sattler <[email protected]> > wrote: > >> >> >> Am 14. September 2015 22:25:00 MESZ, schrieb Pau Garcia i Quiles < >> [email protected]>: >> >Hello, >> > >> >Have you tried >> > >> >set_property(TARGET ${PrjName0} PROPERTY COMPILE_DEFINITIONS_DEBUG >> >-DATEST) >> >> That would be the right thing for add_definitions() but not here. >> He could try with generator expressions though. >> >> > >> >On Mon, Sep 14, 2015 at 9:35 PM, Carl Poirier >> ><[email protected]> >> >wrote: >> > >> >> Hi folks, >> >> >> >> I need some help setting the COMPILE_DEFINITIONS_<CONFIG>. I'm using >> >the >> >> Visual Studio 2008 generator. I use this command to do so which I >> >took in >> >> the notes <http://www.cmake.org/Wiki/CMake_2.6_Notes> when the >> >feature >> >> was added: >> >> >> >> set_property(TARGET ${PrjName0} PROPERTY COMPILE_DEFINITIONS_DEBUG >> >ATEST) >> >> >> >> Then, once the solution and project is generated, I go into the >> >project >> >> properties under the C++ preprocessor and I can't see the define. >> >Removing >> >> the configuration name does set it correctly for all of them, so it >> >leads >> >> me to believe the rest of my CMakeLists.txt is fine: >> >> >> >> set_property(TARGET ${PrjName0} PROPERTY COMPILE_DEFINITIONS ATEST) >> >> >> >> So is this supposed to work? >> >> >> >> Thank you, >> >> >> >> Carl >> >> >> >> -- >> >> >> >> Powered by www.kitware.com >> >> >> >> Please keep messages on-topic and check the CMake FAQ at: >> >> http://www.cmake.org/Wiki/CMake_FAQ >> >> >> >> Kitware offers various services to support the CMake community. For >> >more >> >> information on each offering, please visit: >> >> >> >> CMake Support: http://cmake.org/cmake/help/support.html >> >> CMake Consulting: http://cmake.org/cmake/help/consulting.html >> >> CMake Training Courses: http://cmake.org/cmake/help/training.html >> >> >> >> Visit other Kitware open-source projects at >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> http://public.kitware.com/mailman/listinfo/cmake >> >> >> >> -- >> >> Powered by www.kitware.com >> >> Please keep messages on-topic and check the CMake FAQ at: >> http://www.cmake.org/Wiki/CMake_FAQ >> >> Kitware offers various services to support the CMake community. For more >> information on each offering, please visit: >> >> CMake Support: http://cmake.org/cmake/help/support.html >> CMake Consulting: http://cmake.org/cmake/help/consulting.html >> CMake Training Courses: http://cmake.org/cmake/help/training.html >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/cmake >> > >
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
