-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial integration of download from cmake, add cpack config file #2
Conversation
Discussed in issue #1. I'd like to avoid downloading dependencies with CMake. I want to keep the release packages as standalone, including pre-downloaded libraries and pre-generated manpages so as to have as few external dependencies as possible (currently only CMake itself.) The |
Yeah you are right, but there is no difference in convenience with I totaly understand it takes way to much time to support distro X,Y,Z and platform A,B,C. We could also keep this as a reference and close as-is. Then I will fork the latest release and integrate my changes as needed at Dual Inventive organisation and feature-branch. So our effort will not be lost-in-battle. Let me know what you think. |
I will close this, as this will be solved for the project in a different way. |
Having thought this over, I think you're right that CMake should handle fetching dependencies and generating man pages. The build process should not be so different between the repository and release packages, and the half-baked shell scripts for doing these things need to go. I'm looking at building off of this PR and adding the ability to generate man pages if md2man-roff is installed, this way I can get rid of |
I use CMake in production environment where every build results in a debian package and is automaticly pushed and pgp-signed and added to out own repository. So when you develop and release it automaticly results in good packages :+). |
This is WIP, hopefully finish in the upcoming week.