2010/5/17 Tyler Roscoe <[email protected]>: > 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 _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
