https://github.com/retifrav/cmake-cpack-example
An example project of using CPack
https://github.com/retifrav/cmake-cpack-example
cmake cpack cpp
Last synced: 2 months ago
JSON representation
An example project of using CPack
- Host: GitHub
- URL: https://github.com/retifrav/cmake-cpack-example
- Owner: retifrav
- License: gpl-3.0
- Created: 2021-09-11T19:53:54.000Z (about 4 years ago)
- Default Branch: master
- Last Pushed: 2023-10-07T09:59:05.000Z (almost 2 years ago)
- Last Synced: 2024-05-01T21:33:02.513Z (over 1 year ago)
- Topics: cmake, cpack, cpp
- Language: CMake
- Homepage:
- Size: 43.9 KB
- Stars: 14
- Watchers: 4
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE
Awesome Lists containing this project
README
# CMake CPack example
An example CMake project to demonstrate creating packages with CPack.
More details in the [following article](https://decovar.dev/blog/2021/09/23/cmake-cpack-package-deb-apt/).
## Some issues
As the time passed and I learned a bit more CMake, I realized that some things in these example projects are not entirely correct and could do with certain improvements. Neither affect the main topic of using CPack, so that is good, but still be aware of them just in case:
- libraries are hardcoded to `STATIC`, which is rarely a good idea. But at least it is somewhat understandable in case of Windows, because there are no DLL exports;
- there is no real need to split the installation module into `InstallingGeneral.cmake` and `InstallingConfigs.cmake`, it should be just one `Installing.cmake`;
- the "*generate the export targets for the build tree*" installation step is rather useless, so it probably should be removed;
- the `DESTINATION` for CMake configs should probably be `share/${PROJECT_NAME}` instead of `cmake`, although both work equally fine;
- every library subproject sets `DEBUG_POSTFIX`, while it should be set just once in the top-level project via `CMAKE_DEBUG_POSTFIX` (*but also explicitly for every executable*);
- the libraries targets namespace is set in every subproject. Instead it should be set just once in the top-level project;
- `CMAKE_MODULE_PATH` is set in every subproject. There is no need for that, it is enough to set it once in the top-level project;
- there should be no checks for top-level project and its variables, as libraries are already part of the project, and they shouldn't be meant to be built "separately" (*there is `--target` for that*).
Since the current setup builds and packs fine, I won't be fixing these issues, as that might affect the way example works, and I unfortunately don't have time to test that properly.