(probably a newbie question, but google didn't show anything relevant and answered)
I have a project that includes a third party library (Poco), and then my application that links to it. Everything is built from a single top level CMakeLists.txt file. Poco is includes using add_subdirectory(), the application with include(). However I need to run the install phase of Poco before the application can link to the library - its the install phase of Poco that copies the headers and libraries from all its many sub-directories into the single LIBRARY_OUTPUT_PATH. What's the best way of telling my application not to depend on the build of PocoFoundaton, but the install of all of the Poco project ? Of course there is no global Poco/install target - so I guess one solution would be to work with the Poco team to add that target into their CMakeLists. Are there any other approaches ? Thanks richard.
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
