Hello Brad, On 30/07/14 15:32, Brad King wrote: > Thanks. While reviewing the commits in 'next' again I realized > that assuming paths are relative to CMAKE_BINARY_DIR may not be > correct. Some projects may be nested inside others, and the > CMAKE_BINARY_DIR may not be the proper location for a nested > project. Instead the BUILD_TREE option should be followed by > another argument specifying the base for relative paths, i.e. > the in-build-tree prefix.
I updated the CMakePackageConfigHelpers_build_tree with the requested changed, I'm not sure how to handle this, since the branch is already merged in next, so I added 2 commits that can be squashed to the previous ones: http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=fcdb23e0 http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=77e64799 Can you please review the changes and tell me if I can merge them to next? Thanks. Cheers, Daniele -- 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-developers
