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

72 lines
2.4 KiB
CMake
Raw Normal View History

Add the target_include_directories command. This is a convenience API to populate the corresponding properties.
2013-01-02 02:20:04 +04:00
cmake_minimum_required(VERSION 2.8)
project(target_include_directories)
file(MAKE_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/privateinclude")
file(WRITE "${CMAKE_CURRENT_BINARY_DIR}/privateinclude/privateinclude.h" "#define PRIVATEINCLUDE_DEFINE\n")
file(MAKE_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/publicinclude")
file(WRITE "${CMAKE_CURRENT_BINARY_DIR}/publicinclude/publicinclude.h" "#define PUBLICINCLUDE_DEFINE\n")
file(MAKE_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/interfaceinclude")
file(WRITE "${CMAKE_CURRENT_BINARY_DIR}/interfaceinclude/interfaceinclude.h" "#define INTERFACEINCLUDE_DEFINE\n")
file(MAKE_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/poison")
file(WRITE "${CMAKE_CURRENT_BINARY_DIR}/poison/common.h" "#error Should not be included\n")
file(MAKE_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/cure")
file(WRITE "${CMAKE_CURRENT_BINARY_DIR}/cure/common.h" "#define CURE_DEFINE\n")
add_executable(target_include_directories
"${CMAKE_CURRENT_SOURCE_DIR}/main.cpp"
)
target_include_directories(target_include_directories
PRIVATE "${CMAKE_CURRENT_BINARY_DIR}/privateinclude"
PUBLIC "${CMAKE_CURRENT_BINARY_DIR}/publicinclude"
INTERFACE "${CMAKE_CURRENT_BINARY_DIR}/interfaceinclude"
)
target_include_directories(target_include_directories
PUBLIC "${CMAKE_CURRENT_BINARY_DIR}/poison"
)
target_include_directories(target_include_directories
Remove use of TARGET_DEFINED from target_include_directories test. Change the unit test introduced in commit 24dcf0c0 (Make sure generator expressions can be used with target_include_directories., 2013-01-16) to not use the expression, but still test the appropriate code.
2013-02-25 18:24:15 +04:00
BEFORE PUBLIC "$<$<STREQUAL:$<TARGET_PROPERTY:target_include_directories,TYPE>,EXECUTABLE>:${CMAKE_CURRENT_BINARY_DIR}/cure>"
Make sure generator expressions can be used with target_include_directories. Handle the case that a generator expression is used before treating a non-target as an error.
2013-01-17 01:16:46 +04:00
)
Remove use of TARGET_DEFINED from target_include_directories test. Change the unit test introduced in commit 24dcf0c0 (Make sure generator expressions can be used with target_include_directories., 2013-01-16) to not use the expression, but still test the appropriate code.
2013-02-25 18:24:15 +04:00
# Has no effect because the target type is not SHARED_LIBRARY:
Make sure generator expressions can be used with target_include_directories. Handle the case that a generator expression is used before treating a non-target as an error.
2013-01-17 01:16:46 +04:00
target_include_directories(target_include_directories
Remove use of TARGET_DEFINED from target_include_directories test. Change the unit test introduced in commit 24dcf0c0 (Make sure generator expressions can be used with target_include_directories., 2013-01-16) to not use the expression, but still test the appropriate code.
2013-02-25 18:24:15 +04:00
BEFORE PUBLIC "$<$<STREQUAL:$<TARGET_PROPERTY:target_include_directories,TYPE>,SHARED_LIBRARY>:${CMAKE_CURRENT_BINARY_DIR}/poison>"
Add the target_include_directories command. This is a convenience API to populate the corresponding properties.
2013-01-02 02:20:04 +04:00
)
add_executable(consumer
"${CMAKE_CURRENT_SOURCE_DIR}/consumer.cpp"
)
target_include_directories(consumer
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
PRIVATE
$<TARGET_PROPERTY:target_include_directories,INTERFACE_INCLUDE_DIRECTORIES>
target_include_directories: Allow relative path with genex Treat paths which are relative and which contain a generator expression which is not at the beginning as relative to the source directory. This matches the behavior of paths which are relative but contain no generator expression at all. Previously this would generate a relative path with the IMPORTED target on export(), which would be a reported as a non-existent path on import. If used directly in the buildsystem, it would be reported as a relative path, which is also an error. There is no need for a policy in this case.
2013-11-26 05:38:55 +04:00
relative_dir
relative_dir/$<TARGET_PROPERTY:NAME>
Add the target_include_directories command. This is a convenience API to populate the corresponding properties.
2013-01-02 02:20:04 +04:00
)
Allow target commands to be invoked with no items (#14325). Code such as target_include_directories(foo PRIVATE ${items}) should not work or break based on whether items is defined or not.
2013-07-31 18:02:07 +04:00
# Test no items
target_include_directories(consumer
PRIVATE
)
target_include_directories(consumer
BEFORE PRIVATE
)
target_include_directories(consumer
SYSTEM BEFORE PRIVATE
)
target_include_directories(consumer
SYSTEM PRIVATE
)
cmTarget: Don't update IMPORTED target compilation properties The include_directories() and add_compile_options() commands should not append to the corresponding target property for IMPORTED targets. This is already the case for add_definitions().
2013-12-26 17:11:23 +04:00
include_directories(${CMAKE_CURRENT_BINARY_DIR})
add_library(imp UNKNOWN IMPORTED)
get_target_property(_res imp INCLUDE_DIRECTORIES)
if (_res)
message(SEND_ERROR "include_directories populated the INCLUDE_DIRECTORIES target property")
endif()