summaryrefslogtreecommitdiff
path: root/Source/cmTargetPropCommandBase.h
diff options
context:
space:
mode:
authorStephen Kelly <steveire@gmail.com>2013-01-21 12:28:27 +0100
committerStephen Kelly <steveire@gmail.com>2013-01-21 12:32:46 +0100
commitb98d14d40016efee420bee26b9795880fdf6a5f8 (patch)
tree7226b6db415fb92680bbefcebf205a21b6175f3f /Source/cmTargetPropCommandBase.h
parent48a4cf21825c9ed5f53ac25d5f4577baaf92d1f7 (diff)
downloadcmake-b98d14d40016efee420bee26b9795880fdf6a5f8.tar.gz
Disallow porcelain to populate includes and defines of IMPORTED targets.
With similar reasoning to the parent commit, as downstreams, we can't determine what $<CONFIG> generator expressions would be appropriate. Upstream would have populated the INTERFACE_INCLUDE_DIRECTORIES with config-specific generator expressions, possibly appropriate for their DEBUG_CONFIGURATIONS. In theory, if we would add include directories for a DEBUG intent, we would have to match the upstream configurations for that. Rather than attempting to discover the appropriate configurations at this time, simplify the feature instead. The use of IMPORTED targets with these commands could still be added in the future if targets would export their DEBUG_CONFIGURATIONS somehow.
Diffstat (limited to 'Source/cmTargetPropCommandBase.h')
-rw-r--r--Source/cmTargetPropCommandBase.h3
1 files changed, 1 insertions, 2 deletions
diff --git a/Source/cmTargetPropCommandBase.h b/Source/cmTargetPropCommandBase.h
index e757f9da12..15a78c9a6d 100644
--- a/Source/cmTargetPropCommandBase.h
+++ b/Source/cmTargetPropCommandBase.h
@@ -32,8 +32,7 @@ public:
const char *prop, ArgumentFlags flags = NO_FLAGS);
private:
- virtual void HandleImportedTargetInvalidScope(const std::string &tgt,
- const std::string &scope) = 0;
+ virtual void HandleImportedTarget(const std::string &tgt) = 0;
virtual void HandleMissingTarget(const std::string &name) = 0;
virtual bool HandleNonTargetArg(std::string &content,