<br><br><div class="gmail_quote">On Fri, Jan 30, 2009 at 5:11 PM, BlinkEye <span dir="ltr"><gentoo@blinkeye.ch></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="Ih2E3d">On Fri, January 30, 2009 14:37, Eric Noulard wrote:<br>
> As far as I know CPack only handles a single per-project package,<br>
> i.e. you may easilly build a package (deb, rpm, tgz etc...) for the WHOLE<br>
> project, even if the project does have subdirectories.<br>
> CPack will package all target, files etc... which are<br>
><br>
<br>
</div>Thanks for elaborating and answering my question. I'm actually trying to generate<br>
different .deb files for a single project (e.g. for different libraries,<br>
executables). Checking out your links it looks like this is not possible at the<br>
moment.<br>
<div><div></div><div class="Wj3C7c"></div></div></blockquote><div>You may want to use custom CPack scripts for different purposes. By default, CPack uses script generated by CMake in top-level directory, but you can write your own one (and as many as you want) and pass it to cpack as command line parameter.<br>
Of course, install components could be great help in packaging. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class="Wj3C7c">
<br>
_______________________________________________<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>