Emulate DESTDIR behavior for per-component PPA deployment #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This enables the combination of the
-DCMAKE_INSTALL_COMPONENTvariable with theDESTDIRconvention of GNUmake install(https://www.gnu.org/prep/standards/html_node/DESTDIR.html).The CMake
OPTION_DEPLOY_DESTDIRoption (actually, a cached string variable) is added for Linux systems that takes the value of theDESTDIRparameter/macro/environment variable and generates one target per component (destdir-deploy-${component}) that calls thepreinstalltarget and later executes the install with theDESTDIRconstruct and the current component.With this extension it is possible to deploy only parts of the CMake components for a debian source package. A typical workflow would be: