Hi, I have a written a cmake module to get dependencies using the cget protocol here:
https://github.com/pfultz2/cmake-get This is different than `ExternelProject`: * `ExternelProject` happens only during build, which allows this module to work in both in config and script mode. * In config mode, the user can just do: cmake_get(<pkg> PREFIX ${CMAKE_CURRENT_BINARY_DIR}/deps) find_package(<pkg> HINTS ${CMAKE_CURRENT_BINARY_DIR}/deps) Since the dependency is available at config time. * A script can be easily written to download the dependencies, which is much better approach to deal with toolchain transitivity, which is a problem that exists with both `ExternelProject` and config mode. * Recipes can be reused for building projects that don't use cmake, or don't follow the standard cmake installation flow. Furthermore, an existing cget recipe can be used as well. Is there interest in this project? Of course, the protocol for getting dependencies could be tweaked as based on feedback. I am the author of both this module and cget so it is possible to update cget to match feedback from the larger cmake community. Thanks, Paul -- 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
