Perhaps it's an idea to add the "INSTALL" requirement to the CPack wiki page, to avoid questions by "dummies" like me. (I wrongly assumed that all targets/libraries/... that were in the build directory would end up in the install package.)
Or add the INSTALL(...) to the hello example, in that way the example can be used to demonstrate "make install" and "make package" (CPack) as well.
Thanks for your help!
Peter.
On 10/20/06, David Cole <[EMAIL PROTECTED]> wrote:
Well if you don't have any INSTALL commands, then there is nothing to
install, right?
CPack is simply a tool that transforms your CMakeLists INSTALL
commands into a packaged setup program... So, yes, you do need INSTALL
commands.
You have to be able to run "make install" and end up with a non-empty
install tree prior to running "make package" successfully.
HTH,
David
On 10/20/06, Peter Visser < [EMAIL PROTECTED]> wrote:
> Hello,
>
> I would like to use CPack to make an install package with NSIS for win32.
>
> I downloaded the hello example
> (http://www.cmake.org/HTML/Examples.html) added
> "INCLUDE(CPack)" to the CMakeLists.txt
> ( http://www.cmake.org/Wiki/CMake:Packaging_With_CPack) and
> tried to run "make package"
>
> However an error occurs, according to the NSIS error log this happens:
> File:
> "e:/Temp/cmake/CMakeExample/build/_CPack_Packages/win32/NSIS/HELLO- 0.1.1-win32\*.*"
> -> no files found.
>
> When tried the same example under linux an empty "HELLO-0.1.1-Linux.tar.gz"
> is created, so I must be doing something wrong.
>
> Do I need to specify a "INSTALL(...)" rule in order to use CPack
> succesfully?
>
> Any help appreciated,
>
> Peter.
>
> _______________________________________________
> CMake mailing list
> [email protected]
> http://www.cmake.org/mailman/listinfo/cmake
>
>
_______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
