On Mon, Aug 17, 2015 at 5:17 PM, James Johnston <jam...@motionview3d.com> wrote:
> [...] Your own CMake projects will be > ExternalProjects to this high-level project and the superbuild would pass > the location to your project via -D<project>_DIR=<location> so that > find_package can locate the Config file. > I think a more convenient and also more conforming solution would be to pass the location of a single install directory (-DCMAKE_INSTALL_PREFIX=...) and pass the same dir also as prefix path (-DCMAKE_PREFIX_PATH=...) to all projects. All the projects of the superbuild will search for dependencies (config modules) in this directory and also install their own config modules into this directory. This directory is best to create inside the superbuild dir (like <superbuild-root>/out) and of course removed from source control. CMAKE_PREFIX_PATH may additionally contain other, central locations for other libraries built outside of the superbuild. Tamas
-- 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
