<br><br><div class="gmail_quote">On Wed, Jun 17, 2009 at 10:02 AM, Tyler Roscoe <span dir="ltr"><<a href="mailto:tyler@cryptio.net">tyler@cryptio.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Wed, Jun 17, 2009 at 09:54:58AM -0700, Richard Offer wrote:<br>
> However I need to run the install phase of Poco before the application can<br>
> link to the library - its the install phase of Poco that copies the headers<br>
> and libraries from all its many sub-directories into the single<br>
> LIBRARY_OUTPUT_PATH.<br>
><br>
</div><div class="im">> Of course there is no global Poco/install target - so I guess one solution<br>
> would be to work with the Poco team to add that target into their<br>
> CMakeLists. Are there any other approaches ?<br>
<br>
</div>If there is no global Poco/install target, how do you "run the install<br>
phase of Poco"?<br>
<font color="#888888"><br>
tyler<br>
</font></blockquote></div><br><br>make install in the Poco build directory.<br><br>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.<br>
<br><br>In previous build systems I've written I have used the phased approach - make headers; make exports; make ; make installer<br><br>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.<br>
<br>Is that normal in CMake ? Or is there a better way ?<br><br><br>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.<br>
<br>richard.<br><br><br>