CODEWITHSUNDEEP
linuxcmakepackagingcpack
Meysam
Meysam

Reputation: 18117

CPack: "make package" generates an empty deb package

I'm using the combination of CMake and CPack to generate a package. This is the CPack part of my CMake file:

set(CPACK_GENERATOR "DEB")
SET(CPACK_PACKAGE_VENDOR "Company")
set(CPACK_COMPONENTS_ALL exe link configs lastversion script log monitor)
set(CPACK_PACKAGE_FILE_NAME "${PRODUCT}")
set(CPACK_PACKAGE_VERSION ${MAJOR}.${MINOR}.${PATCH})
set(CPACK_PACKAGE_VERSION_MAJOR ${MAJOR})
set(CPACK_PACKAGE_VERSION_MINOR ${MINOR})
set(CPACK_PACKAGE_VERSION_PATCH ${PATCH})
set(CPACK_DEBIAN_PACKAGE_DEPENDS "")
set(CPACK_PACKAGE_DESCRIPTION "Some Description")
set(CPACK_PACKAGE_CONTACT "[email protected]")

include(CPack)

On my computer (64bit), executing "make package" gives me a fully functional .deb package:

Run CPack packaging tool...
CPack: Create package using DEB
CPack: Install projects
CPack: - Run preinstall target for: XXX
CPack: - Install project: XXX
CPack: Create package
CPack: - package: /home/username/xxx-B-4.0.0.deb generated.

But on another system (32bit Lenny), executing the same command using the same CMake file, gives me an empty .deb package. What could be wrong?

The output of 32bit system:

Run CPack packaging tool...
CPack: Create package using DEB
CPack: Install projects
CPack: - Run preinstall target for: XXX
CPack: - Install project: XXX
CPack: Compress package
CPack: Finalize package
CPack: Package /home/username/xxx-B-4.0.0.deb generated.

I've highlighted the difference between the outputs.

Upvotes: 0

Views: 1521

Answers (1)

Barth
Barth

Reputation: 15715

Try To use the same version, i.e. 2.8, on both platforms. It might be that in 2.6 there is an extra parameter required or something along this line.

Upvotes: 1

Related Questions