diff options
| author | Eric NOULARD <eric.noulard@gmail.com> | 2012-05-14 21:29:42 (GMT) |
|---|---|---|
| committer | Eric NOULARD <eric.noulard@gmail.com> | 2012-05-14 21:29:42 (GMT) |
| commit | 47f0dbd70b83ccb5e314abee5feded2ed50a23fb (patch) | |
| tree | b3821ced0886a295429aa3e014e4f7abf087a5aa /Source/CPack/cmCPackNSISGenerator.h | |
| parent | 6ba055bacdce1cdf7a74008b980440027f275d94 (diff) | |
| download | CMake-47f0dbd70b83ccb5e314abee5feded2ed50a23fb.zip CMake-47f0dbd70b83ccb5e314abee5feded2ed50a23fb.tar.gz CMake-47f0dbd70b83ccb5e314abee5feded2ed50a23fb.tar.bz2 | |
CPack add necessary check to detect/warns/error on ABSOLUTE DESTINATION
The [usually] wrong usage of absolute DESTINATION in INSTALL rules
keeps popping-up on the ML. We shall have some way to:
1) easily detect it.
2) forbids this for some CPack generator like NSIS
In fact it should certainly be forbidden for *any* generators
when used on Windows but we may implements that on top of the current
patch.
The patch ask the task to the generated cmake_install.cmake scripts.
Those scripts are a little bit more complicated with that but
iff there are absolute DESTINATION. This cost nothing if relative
DESTINATION are used.
Two new vars are introduced (and documented to handle that):
CPACK_WARN_ON_ABSOLUTE_INSTALL_DESTINATION
and
CPACK_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION
Diffstat (limited to 'Source/CPack/cmCPackNSISGenerator.h')
| -rw-r--r-- | Source/CPack/cmCPackNSISGenerator.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/Source/CPack/cmCPackNSISGenerator.h b/Source/CPack/cmCPackNSISGenerator.h index c2987d0..8224854 100644 --- a/Source/CPack/cmCPackNSISGenerator.h +++ b/Source/CPack/cmCPackNSISGenerator.h @@ -45,6 +45,7 @@ protected: std::vector<std::string>& dirs); enum cmCPackGenerator::CPackSetDestdirSupport SupportsSetDestdir() const; + virtual bool SupportsAbsoluteDestination() const; virtual bool SupportsComponentInstallation() const; /// Produce a string that contains the NSIS code to describe a |