Hi,<br>I use use CPack to generate multiple packages (abusing COMPONENT).<br>My project dirs are like that:<br>Libs/<br>ProjectA/<br>ProjectB/<br><br>ProjectA
and B need the libs from Libs. So when I create a package for ProjectA
/ ProjectB I need the packaging to include libs from Libs.
<br>So in Libs/CMakeLists.txt:<br>INSTALL(<br> PROGRAMS ${LIBRARY_OUTPUT_PATH}/libLibs<div id="1fi4" class="ArwC7c ckChnd">.so<br> DESTINATION "usr/lib"<br> COMPONENT "Libs"<br> )<br>In my ProjectA/CMakeLists.txt:
<br># To allow different
CPackConfig.cmake files (not over-written by another project<br>SET( CPACK_OUTPUT_CONFIG_FILE "${PROJECT_BINARY_DIR}/CPackConfig.cmake" )<br>INSTALL(<br> PROGRAMS ${EXECUTABLE_OUTPUT_PATH}/ProjectsA<br> DESTINATION "usr/bin"
<br> COMPONENT "ProjectA"<br> )<br>And in my CMakeLists.txt:<br>ADD_CUSTOM_TARGET(<br> packageProjectA<br> COMMAND cmake -E remove_directory ${CMAKE_INSTALL_PREFIX}<br> COMMAND cmake -DCOMPONENT="ProjectA" -P cmake_install.cmake
<br> COMMAND cmake -DCOMPONENT="Libs" -P cmake_install.cmake<br> COMMAND cpack --config ${PROJECT_BUILD_DIR}/GasSensorController/CPackConfig.cmake<br> )<br><br>That's very dirty but works for me.<br>
Raph</div><br><br><div class="gmail_quote">On Jan 17, 2008 7:35 AM, Eric Noulard <<a href="mailto:eric.noulard@gmail.com">eric.noulard@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2008/1/16, Filipe Sousa <<a href="mailto:natros@gmail.com">natros@gmail.com</a>>:<br><div class="Ih2E3d">> Ted Berg wrote:<br>> > Filipe Sousa wrote:<br>> ><br>> > I aplogize, my initial post wasn't terribly clear. I'm currently
<br>> > generating, for example, the following packages:<br>> ><br>> > foo-sdk-1.0.0.zip<br>> > foo-qa-tools-1.0.0.zip<br>> > foo-killer-app-1.0.0.zip<br>> ><br>> > These packages have different content and are targeted at different
<br>> > users. I initially thought I could duplicate this behavior using<br>> > COMPONENTs in CMake's install command, but it's not behaving how I would<br>> > like and I'm pretty sure that what I want is abusing the feature (at best).
<br><br></div>I am really interested in how you did emulate the feature using<br>INSTALL / COMPONENT.<br>Do you have any CMakeLists.txt and/or CMake macro scripts examples?<br>Could you tell us how with those do you invoke cpack or make
<br>in order to build you packages?<br><div class="Ih2E3d"><br>> Ah! I know what you mean but I don't think there is an easy way of doing<br>> that. But it's very useful split a package into small packages (debian
<br>> way -- libfoo.tar.gz, foo.tar.gz, libfoo-dev, foo-docs).<br><br></div>I think it's useful too, but is it specific generator task or is<br>it CPack task to do this? (this is an open question).<br><font color="#888888">
<br><br>--<br>Erk<br></font><div><div></div><div class="Wj3C7c">_______________________________________________<br>CMake mailing list<br><a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br><a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">
http://www.cmake.org/mailman/listinfo/cmake</a><br></div></div></blockquote></div><br>