[CMake] The output of cpack is an empty file
pellegrini
pellegrini at ill.fr
Tue Sep 27 05:04:09 EDT 2011
Hello everybody,
I would like to use cpack in order to gather a set of executables (built
statically) into a single archive that could be extracted everywhere the
user wants.
My project architecture is the following:
collections\
CMakeLists.txt
prog1\
CMakeLists.txt + source files
prog2\
CMakeLists.txt + source files
prog3\
CMakeLists.txt + source files
where each CMakeLists.txt files are stand-alone CMake projects
(historically each program still has to be "buildable" alone) that
produces prog1, prog2, prog3 executables.
My main CMakeLists.txt looks like:
##########################################
project(collections)
add_subdirectory(prog1)
add_subdirectory(prog2)
add_subdirectory(prog3)
set(CPACK_GENERATOR "ZIP")
set(CPACK_PACKAGE_DESCRIPTION_FILE "${CMAKE_CURRENT_SOURCE_DIR}/README")
set(CPACK_PACKAGE_NAME "collection of progs)
set(CPACK_PACKAGE_FILE_NAME "collections")
set(CPACK_PACKAGE_VERSION_MAJOR "1")
set(CPACK_PACKAGE_VERSION_MINOR "0")
set(CPACK_PACKAGE_EXECUTABLES "collections")
include(CPack)
##########################################
when running cmake and then nmake package, the built is done, cpack is
launched but the resulting archive is empty. No README inside and more
disturbing no
prog1, prog2, prog3 executables. I may have miss something when reading
the examples but I still have not found what. Would you have any idea ?
thanks a lot
Eric
--
Eric Pellegrini
Calcul Scientifique
Institut Laue-Langevin
Grenoble, France
More information about the CMake
mailing list