[CMake] How does CPACK decide what goes into release packages?

[kent williams]

Platform: OS X 10.5.8. We also want to support Linux and Windows, but
are doing OS X first because it's usally the crankiest to get working.

cpack version 2.9.20100511

Using PackageMaker and Tar for generators.

I don't have it all worked out, but I think the problems I'm having
aren't CPack's fault.  Someone else did the setup for CPack, and
copied a bunch of complicated stuff from some other project, without
understanding what it did, and then never debugged it.  Now I'm having
to actually learn how to use CPack properly to unravel it all.

On Tue, May 18, 2010 at 1:29 AM, Eric Noulard <eric.noulard at gmail.com> wrote:
> 2010/5/17 Tyler Roscoe <tyler at cryptio.net>:
>> On Mon, May 17, 2010 at 12:53:34PM -0500, kent williams wrote:
>>> "Internally, CPack will use CMake's install mechanism to automatically
>>> populate the package."
>>
>> Right. Mostly, all that CPack does is call "make install" on your
>> project with a special CMAKE_INSTALL_PREFIX.
>>
>>> but when I add
>>> include(CPack)
>>> and then run
>>> make package
>>>
>>> It generates empty install packages.
>
> I'll add a bunch of questions:
>
> 1) Which platform (Unix, Windows, MacOs etc...)
> 2) What is the cpack/cmake version  (output of cpack --version)
> 3) Which CPack generator are you using (ZIP, TGZ, DEB, NSIS, PackageMaker,...)
>
>>> The only target (for now) that needs to go into the package is a
>>> single statically linked executable, which is referenced with a cmake
>>> install command:
>>>
>>> INSTALL(TARGETS BRAINSFit DESTINATION bin)
>>
>> What does your project do when you "make install"?
>>
>> tyler
>
> --
> Erk
> Membre de l'April - « promouvoir et défendre le logiciel libre » -
> http://www.april.org
>