kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
CMake/Tests/CMakeCommands/target_compile_definitions/CMakeLists.txt

31 lines
787 B
CMake
Raw Normal View History

Add the target_compile_definitions command. This is a convenience API to populate the corresponding properties.
2013-01-08 03:34:41 +04:00
cmake_minimum_required(VERSION 2.8)
project(target_compile_definitions)
add_executable(target_compile_definitions
"${CMAKE_CURRENT_SOURCE_DIR}/main.cpp"
)
target_compile_definitions(target_compile_definitions
PRIVATE MY_PRIVATE_DEFINE
PUBLIC MY_PUBLIC_DEFINE
INTERFACE MY_INTERFACE_DEFINE
)
add_executable(consumer
"${CMAKE_CURRENT_SOURCE_DIR}/consumer.cpp"
)
Add the $<LINKED:...> generator expression. This is both a short form of using a TARGET_DEFINED expression together with a TARGET_PROPERTY definition, and a way to strip non-target content from interface properties when exporting.
2013-01-31 02:38:04 +04:00
add_library(linked UNKNOWN IMPORTED)
set_property(TARGET linked PROPERTY
INTERFACE_COMPILE_DEFINITIONS "MY_LINKED_DEFINE")
Add the target_compile_definitions command. This is a convenience API to populate the corresponding properties.
2013-01-08 03:34:41 +04:00
target_compile_definitions(consumer
Don't allow targets args in the new target commands.
2013-01-29 20:43:28 +04:00
PRIVATE $<TARGET_PROPERTY:target_compile_definitions,INTERFACE_COMPILE_DEFINITIONS>
Add the TARGET_DEFINED generator expression This tests whether the parameter is a usable target.
2012-11-20 02:56:12 +04:00
$<$<TARGET_DEFINED:notdefined>:SHOULD_NOT_BE_DEFINED>
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.
2013-01-21 15:28:27 +04:00
$<$<TARGET_DEFINED:target_compile_definitions>:SHOULD_BE_DEFINED>
Add the $<LINKED:...> generator expression. This is both a short form of using a TARGET_DEFINED expression together with a TARGET_PROPERTY definition, and a way to strip non-target content from interface properties when exporting.
2013-01-31 02:38:04 +04:00
$<LINKED:linked>
Make subclasses responsible for joining content. This way we can add handling of relative/absolute paths and of -D in compile definitions.
2013-01-29 20:23:31 +04:00
-DDASH_D_DEFINE
Add the target_compile_definitions command. This is a convenience API to populate the corresponding properties.
2013-01-08 03:34:41 +04:00
)