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

[Tyler Roscoe]

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.
> 
> 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