Hi Brian, ExternalProject_Add has a DEPENDS option. What you can do is let X depend on Y and use the CMAKE_CACHE_ARGS option to provide the include path, or use the buildsystem in project X to find the headers itself.
Regards,
Micha
On 03/19/2014 03:11 AM, Brian Lewis wrote:
> If X brings in Y as an external project, and Y brings in Z as an
> external project, is there some way for Y to communicate information
> about Z back to X, e.g., some include directory?
>
> My situation is, X doesn't know anything about Z, but needs to be able
> to find one of Z's headers. I wish I could add Y as an external project
> and then include_directories(${Y_INCLUDE_DIRS}).
signature.asc
Description: OpenPGP digital signature
-- 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
