b98d14d400
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.
24 lines
586 B
CMake
24 lines
586 B
CMake
|
|
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"
|
|
)
|
|
|
|
target_compile_definitions(consumer
|
|
PRIVATE target_compile_definitions importedlib
|
|
$<$<TARGET_DEFINED:notdefined>:SHOULD_NOT_BE_DEFINED>
|
|
$<$<TARGET_DEFINED:target_compile_definitions>:SHOULD_BE_DEFINED>
|
|
)
|