cpack

Name and description of multiple debian packages with CMake and CPack

久未见 提交于 2019-12-05 16:01:33
I am currently trying to generate more than one debian package from my project. My only problem with this is setting the name, description, group and so forth of the packages. # -------------------------------------------------------------- # Required CMake version # -------------------------------------------------------------- CMAKE_MINIMUM_REQUIRED (VERSION 2.8) # -------------------------------------------------------------- # Project name # -------------------------------------------------------------- PROJECT (MyProject) # -------------------------------------------------------------- #

Can CMake/CPack generate multiple NSIS installers for a single project?

≯℡__Kan透↙ 提交于 2019-12-05 07:46:46
I have a single project (with sub-projects) for which I would like to generate multiple NSIS installer executables, instead of having multiple components listed in a single NSIS installer. Is this possible? Or do I need to organize my code into separate projects? One could provide a CMake attribute e.g. COMPONENT which can be set to a value from a predefined set of package names like: COMPONENT_1|COMPONENT_2|...COMPONENT_X The package name could even be a name that does not correspond to a single component name but a set of components that would be added in the CPACK_COMPONENTS_ALL. If the

CPack tries to build all targets

风流意气都作罢 提交于 2019-12-05 07:06:22
I have a CMake project composed of one root CMakeLists and multiple sub- CMakeLists (one for each project). I am trying to use CPack to generate a .deb file for one of these projects (APP_client). Yet, when I try to run CPack , it first runs a 'preinstall' and try to build all targets. I want to build only the required targets and their dependencies. Here is what I added to one of my CMakeLists : if(UNIX) INSTALL( TARGETS ${PROJECT_NAME} COMPONENT ${PROJECT_NAME} DESTINATION ${PROJECT_INSTALL_PATH} ) SET(CPACK_PACKAGE_DIRECTORY ${CMAKE_BINARY_DIR}/../deb) SET(CPACK_GENERATOR "DEB") SET(CPACK

CPack DEB generator: control-file-has-bad-permissions mdsums 0644 != 0644

孤者浪人 提交于 2019-12-05 04:26:13
I am developing small console application and I was trying to create Ubuntu package using CPack. Ubuntu version is 13.04 and my main CPack file is below. Package is created correctly, but while trying to install it using graphic interface (basically double click on deb file in Ubuntu) following warning appears: Package is of bad quality control-file-has-bad-permissions mdsums 0644 != 0644 Does anybody know what is the reason of that? And more importantly, how to fix it? CMake version is 2.8.10.1 but I have also tried to use 2.8.11.2 and nothing has changed. I have seen, that they had similar

CMake-CPack Package Installation Path Nightmare

梦想与她 提交于 2019-12-03 15:20:18
问题 I've been frustrated by the the CMake-CPack for almost one week. The bad thing is the CMake-CPack online documentation does not document this part well. After googling, I found this variables to use: CPACK_PACKAGING_PREFIX # NOT documented CMAKE_INSTALL_PREFIX # Documented, but the behavior seems weird CPACK_INSTALL_PREFIX # NOT documented CPACK_PACKAGE_INSTALL_DIRECTORY # Documented, but this variable does NOT work as the online document described CPACK_PACKAGING_INSTALL_PREFIX # NOT

CMake-CPack Package Installation Path Nightmare

扶醉桌前 提交于 2019-12-03 05:00:32
I've been frustrated by the the CMake-CPack for almost one week. The bad thing is the CMake-CPack online documentation does not document this part well. After googling, I found this variables to use: CPACK_PACKAGING_PREFIX # NOT documented CMAKE_INSTALL_PREFIX # Documented, but the behavior seems weird CPACK_INSTALL_PREFIX # NOT documented CPACK_PACKAGE_INSTALL_DIRECTORY # Documented, but this variable does NOT work as the online document described CPACK_PACKAGING_INSTALL_PREFIX # NOT documented What I am trying to do is: package a Debian package using fakeroot make package , when the package

“make dist” equivalent in CMake

走远了吗. 提交于 2019-11-30 07:07:50
According to FAQ , CMake doesn't create a make dist target and source package can be created using CPack. But CPack just makes a tarball of the source directory with all files that don't match patterns in CPACK_SOURCE_IGNORE_FILES . On the other hand, make dist generated by autotools bundles only files it knows about, mostly sources needed for compilation. Anyone has a smart way of making a source package with only files that are specified in CMakeLists.txt (and its dependencies)? I've been thinking about this for a while and I won't pretend I can simulate a make dist without having this

How to build debian package with CPack to execute setup.py?

≯℡__Kan透↙ 提交于 2019-11-29 23:13:06
Until now, my project had only .cpp files that were compiled into different binaries and I managed to configure CPack to build a proper debian package without any problems. Recently I wrote a couple of python applications and added them to the project, as well as some custom modules that I would also like to incorporate to the package. After writing a setup.py script, I'm wondering how to add these files to the CPack configuration in a way that setup.py get's executed automatically when the user installs the package on the system with dpkg -i package.deb . I'm struggling to find relevant

How to create an installer with CMake + CPack + NSIS on Windows?

对着背影说爱祢 提交于 2019-11-29 23:05:10
I'd like to create a cross-platform installer for a C++ based system I am building. I use CMake to build everything, and it would be great if I could use CPack to make the installer. I already have CPack working on OSX, but I cannot get it to work on Windows. To make things easier, I tried to get the example at http://www.cmake.org/Wiki/CMake:Packaging_With_CPack to work with the NSIS installer software. I cannot find the NSIS installer anywhere after configuring (with VS 2010 Win64 generator). Maybe I am confused, but I thought it would be possible to create the installation package with only

“make dist” equivalent in CMake

≡放荡痞女 提交于 2019-11-29 08:32:16
问题 According to FAQ, CMake doesn't create a make dist target and source package can be created using CPack. But CPack just makes a tarball of the source directory with all files that don't match patterns in CPACK_SOURCE_IGNORE_FILES . On the other hand, make dist generated by autotools bundles only files it knows about, mostly sources needed for compilation. Anyone has a smart way of making a source package with only files that are specified in CMakeLists.txt (and its dependencies)? 回答1: I've