> 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.
> Of course, install components could be great h
On Fri, Jan 30, 2009 at 5:11 PM, BlinkEye wrote:
> On Fri, January 30, 2009 14:37, Eric Noulard wrote:
> > As far as I know CPack only handles a single per-project package,
> > i.e. you may easilly build a package (deb, rpm, tgz etc...) for the WHOLE
> > project, even if the project does have sub
On Fri, January 30, 2009 14:37, Eric Noulard wrote:
> As far as I know CPack only handles a single per-project package,
> i.e. you may easilly build a package (deb, rpm, tgz etc...) for the WHOLE
> project, even if the project does have subdirectories.
> CPack will package all target, files etc...
2009/1/30 BlinkEye :
> Hello
>
> I seem not able to find an example of how to generate .deb files with cpack
> for
> different subdirectories of a project. Is this possible and if so, how?
As far as I know CPack only handles a single per-project package,
i.e. you may easilly build a package (deb,
Hello
I seem not able to find an example of how to generate .deb files with cpack for
different subdirectories of a project. Is this possible and if so, how?
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
