summaryrefslogtreecommitdiff
path: root/Source/cmInstallCommand.cxx
diff options
context:
space:
mode:
authorStephen Kelly <steveire@gmail.com>2013-07-29 15:16:15 +0200
committerStephen Kelly <steveire@gmail.com>2013-07-29 15:16:15 +0200
commit72d13ff4826ff3e120fe2d052495b0806c2a5b90 (patch)
tree0450cc1c5c941733beb91c636669be02b7162786 /Source/cmInstallCommand.cxx
parent650e61f833c2cc3ace8405a22eb80a10cfc6187c (diff)
downloadcmake-72d13ff4826ff3e120fe2d052495b0806c2a5b90.tar.gz
install: Remove error condition using INCLUDES DESTINATION without EXPORT.
Commit 650e61f8 (Add a convenient way to add the includes install dir to the INTERFACE., 2013-01-05) introduced an error case for using the install(TARGETS) command with specified INCLUDES DESTINATION, but no specified EXPORT set. It is convenient to use a variable to set the various destinations for different outputs (as KDE does), and some targets such as executables are installed but not exported. This was triggering the error case, but as it is a common case, remove the error.
Diffstat (limited to 'Source/cmInstallCommand.cxx')
-rw-r--r--Source/cmInstallCommand.cxx7
1 files changed, 0 insertions, 7 deletions
diff --git a/Source/cmInstallCommand.cxx b/Source/cmInstallCommand.cxx
index 4649eda149..0faf1d4de8 100644
--- a/Source/cmInstallCommand.cxx
+++ b/Source/cmInstallCommand.cxx
@@ -295,13 +295,6 @@ bool cmInstallCommand::HandleTargetsMode(std::vector<std::string> const& args)
return false;
}
- if(!includesArgs.GetIncludeDirs().empty() && exports.GetString().empty())
- {
- this->SetError("TARGETS given INCLUDES DESTINATION, but EXPORT set "
- "not specified.");
- return false;
- }
-
// Enforce argument rules too complex to specify for the
// general-purpose parser.
if(archiveArgs.GetNamelinkOnly() ||