CMake/Tests/RunCMake/include_directories/RunCMakeTest.cmake

include(RunCMake)

run_cmake(NotFoundContent)
run_cmake(DebugIncludes)
run_cmake(TID-bad-target)
run_cmake(SourceDirectoryInInterface)
run_cmake(BinaryDirectoryInInterface)
run_cmake(RelativePathInInterface)
run_cmake(ImportedTarget)
run_cmake(RelativePathInGenex)
GenEx: Fix reporting about not-found include directories and libraries. This fixes a regression introduced in commit 290e92ad (Move GetIncludeDirectories to cmGeneratorTarget, 2012-09-16) which loops over cmGeneratorTargets before they get created, so the container is empty. 2012-10-15 10:27:42 +02:00			`include(RunCMake)`

			`run_cmake(NotFoundContent)`
Add a way to print the origins of used include directories. 2012-12-18 16:16:14 +01:00			`run_cmake(DebugIncludes)`
Whitelist target types in target_{include_directories,compile_definitions} Setting include directories or compile definitions on a target created with add_custom_target does not make sense. 2013-02-08 19:12:45 +01:00			`run_cmake(TID-bad-target)`
install(EXPORT): Ensure clean INTERFACE_INCLUDE_DIRECTORIES Check that source and binary directories are not part of the INTERFACE_INCLUDE_DIRECTORIES for installed IMPORTED targets. This is limited to directories which do not contain generator expressions to evaluate. Such paths can only be checked at time of use of the imported target, which will be done in a follow up patch. 2013-03-24 21:18:17 +01:00			`run_cmake(SourceDirectoryInInterface)`
			`run_cmake(BinaryDirectoryInInterface)`
			`run_cmake(RelativePathInInterface)`
Report an error on IMPORTED targets with a faulty INTERFACE It is considered an error if the INTERFACE_INCLUDE_DIRECTORIES contains a directory which does not exist, which indicates a programmer error by the upstream, or a packaging error. One of the RunCMake.CompatibleInterface tests also needs to be updated due to this change. Non-existant includes were used in the test, but are not needed. 2013-03-24 21:18:21 +01:00			`run_cmake(ImportedTarget)`
Error if linked target has relative paths in INTERFACE_INCLUDE_DIRECTORIES We can do this check only if the TargetName is non-empty, which means that we're evaluating INTERFACE_INCLUDE_DIRECTORIES from a linked dependency which was set using target_link_libraries. It is possible to have relative paths in INCLUDE_DIRECTORIES already in CMake 2.8.10.2, so that part will require a policy to fix. 2013-03-26 18:08:26 +01:00			`run_cmake(RelativePathInGenex)`