On 2018 M01 4, Thu 05:09:54 CET Dave Milter wrote: > Hello, > > If there is some libfoo that I want to use in my project, > and this libfoo has it's own CMakeLists.txt I have 3 options to deal > with such external dependency: > > a) Treat it like every other external dependency and write cmake code > like FindLibFoo.cmake to find libfoo on file system.
This would be a clean solution if you don't want to build libfoo as part of your project. > b)Include this project as git submodule and use ExternalProject to > invoke `cmake` and `cmake --build` This would be a clean solution if you want to build libfoo as part of yur project. > > c)Include this project as git submodule and use add_subdirectory(libfoo) the "parent" project will/can influence the behaviour of libfoo then, I would not recommend this. Or use d) as Alan suggests. Alex -- 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: https://cmake.org/mailman/listinfo/cmake
