On Wed, Jun 17, 2009 at 10:02 AM, Tyler Roscoe <[email protected]> wrote:
> On Wed, Jun 17, 2009 at 09:54:58AM -0700, Richard Offer wrote: > > 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. > > > > 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 ? > > If there is no global Poco/install target, how do you "run the install > phase of Poco"? > > tyler > make install in the Poco build directory. However a make install from the top level doesn't work since it seems its trying to build all the code first and then install it - rather than a phased approach of make install for each component. In previous build systems I've written I have used the phased approach - make headers; make exports; make ; make installer where headers installs all the headers for the entire build, exports builds all the libraries, make then builds all the binaries and make installer builds the installer/packages. Is that normal in CMake ? Or is there a better way ? Part of the root of the question is how to move my mental model of complex make based builds to the cmake model so that I do it the cmake way rather than simply resort to make hacks. 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
