Am I correct in stating that ExternalProject_Add() cannot completely replace find_package()?
e.g. if I point ExternalProject_Add() to download a software package (which uses a CMake build system and exports its targets and provides a <package>-config.cmake file) the only thing this does is to provide a target to download, patch, build, test, install the software in question, yes? It doesn't look for any <project>-config.cmake file, to help setup include dirs, etc., correct? So if a project providing a config.cmake file is downloaded, built etc. with ExternalProject_Add one still needs to then have find_package() to know what include directories need to be added etc. unless I am missing something. Clarification much appreciated. Thanks, Izaak Beekman =================================== (301)244-9367 Princeton University Doctoral Candidate Mechanical and Aerospace Engineering [email protected] UMD-CP Visiting Graduate Student Aerospace Engineering [email protected] [email protected] -- 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://www.cmake.org/mailman/listinfo/cmake
