[cmake-developers] Processing export() at generate-time
Hello, I pushed a export-at-generate-time topic to my clone. It changes the behavior of export() to be executed at generate-time by default, unless the result is include()d (policy CMP0024). This is needed to be able to have multiple dependent export sets in the build directory. I make use of that in my clone of the boost-cmake repo: https://github.com/steveire/BoostCMake/commits/master Any comments on this? Can I merge it to next? 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
Re: [cmake-developers] Processing export() at generate-time
On 10/10/2013 11:10 AM, Stephen Kelly wrote: I pushed a export-at-generate-time topic to my clone. It changes the behavior of export() to be executed at generate-time by default, unless the result is include()d (policy CMP0024). This is needed to be able to have multiple dependent export sets in the build directory. I haven't reviewed every hunk in detail but overall it looks good. It will be nice to have a feature to sell the need for CMP0024 in the same release that introduces the policy. Thanks, -Brad -- 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
Re: [cmake-developers] Processing export() at generate-time
Brad King wrote: On 10/10/2013 11:10 AM, Stephen Kelly wrote: I pushed a export-at-generate-time topic to my clone. It changes the behavior of export() to be executed at generate-time by default, unless the result is include()d (policy CMP0024). This is needed to be able to have multiple dependent export sets in the build directory. I haven't reviewed every hunk in detail but overall it looks good. It will be nice to have a feature to sell the need for CMP0024 in the same release that introduces the policy. To be clear, the topic changes export() to be executed at configure-time, independent of the policy. Only the OLD policy behavior only forces the file to be generated at configure-time instead. I've pushed the topic for dashboard testing. 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
