| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
This is needed for the target_compile_features command, which
may fail at configure time if an invalid feature is specified.
|
| |
|
|
| |
Property names are always generated by CMake and should never be NULL.
|
| |
|
|
|
| |
Drop all GetTerseDocumentation and GetFullDocumentation methods from
commands. The command documentation is now in Help/command/*.rst files.
|
| |
|
|
|
|
| |
This is similar to the include_directories(SYSTEM) signature
in that it allows telling the compiler to ignore warnings from
such headers.
|
| |
|
|
|
| |
This can be used to handle INTERFACE SYSTEM include directories
in particular.
|
| |
|
|
|
|
|
|
| |
Both commit 8a37ebec (Add the target_include_directories command,
2013-01-01) and commit fc61a7a7 (Add the target_compile_definitions
command, 2013-01-08) added command implementations deriving from the new
cmTargetPropCommandBase class. Fix cmTypeMacro declarations of the
inheritance relationship.
|
| |
|
|
|
| |
This way we can add handling of relative/absolute paths and of
-D in compile definitions.
|
| | |
|
| |
|
|
| |
Makes subclasses more dry in upcoming patches.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
|
|
This is a convenience API to populate the corresponding properties.
|
