summaryrefslogtreecommitdiffstats
path: root/Source/cmTargetCompileDefinitionsCommand.cxx
Commit message (Collapse)AuthorAgeFilesLines
* cmTargetPropCommandBase: Change the interface to return bool.Stephen Kelly2014-04-071-1/+2
| | | | | This is needed for the target_compile_features command, which may fail at configure time if an invalid feature is specified.
* Use new cmHasLiteralPrefix functionStephen Kelly2013-11-211-1/+1
|
* Add a SYSTEM parameter to target_include_directories (#14180)Stephen Kelly2013-07-021-1/+1
| | | | | | This is similar to the include_directories(SYSTEM) signature in that it allows telling the compiler to ignore warnings from such headers.
* Rename the IncludeDirectoriesEntry to be more generic.Stephen Kelly2013-02-121-2/+0
|
* Make subclasses responsible for joining content.Stephen Kelly2013-01-291-2/+25
| | | | | This way we can add handling of relative/absolute paths and of -D in compile definitions.
* Don't allow targets args in the new target commands.Stephen Kelly2013-01-291-10/+0
|
* Disallow porcelain to populate includes and defines of IMPORTED targets.Stephen Kelly2013-01-211-5/+3
| | | | | | | | | | | | | | | | 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.
* Add the target_compile_definitions command.Stephen Kelly2013-01-101-0/+57
This is a convenience API to populate the corresponding properties.