Starting with CMake 3.1, and going forward, is add_definitions() still recommended if you have preprocessor definitions you want included in all projects? The evolution of CMake appears to discourage setting global state in favor of relying more on target properties (for includes, definitions, and more).
This usually requires me to create a wrapper function I use in all CMake scripts to generate targets, so it will handle setup common to all projects. Sometimes it's just easier to set global state. What's the desired design and structure intended going forward? -- 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
