kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
CMake/Tests/RunCMake/GeneratorExpression/RunCMakeTest.cmake

41 lines
1.2 KiB
CMake
Raw Normal View History

Add boolean generator expressions Add generator expressions that combine and use boolean test results: $<0:...> = empty string (ignores "...") $<1:...> = content of "..." $<AND:?[,?]...> = '1' if all '?' are '1', else '0' $<OR:?[,?]...> = '0' if all '?' are '0', else '1' $<NOT:?> = '0' if '?' is '1', else '1' These will be useful to evaluate (future) boolean query expressions and condition content on the results. Include tests and documentation.
2012-08-13 17:49:53 +04:00
include(RunCMake)
Add $<CONFIG:...> boolean query generator expression This expression evaluates to '1' or '0' to indicate whether the build configuration for which the expression is evaluated matches tha named configuration. In combination with the "$<0:...>" and "$<1:...>" expressions this allows per-configuration content to be generated.
2012-08-13 18:00:32 +04:00
run_cmake(BadCONFIG)
Add boolean generator expressions Add generator expressions that combine and use boolean test results: $<0:...> = empty string (ignores "...") $<1:...> = content of "..." $<AND:?[,?]...> = '1' if all '?' are '1', else '0' $<OR:?[,?]...> = '0' if all '?' are '0', else '1' $<NOT:?> = '0' if '?' is '1', else '1' These will be useful to evaluate (future) boolean query expressions and condition content on the results. Include tests and documentation.
2012-08-13 17:49:53 +04:00
run_cmake(BadOR)
run_cmake(BadAND)
run_cmake(BadNOT)
GenEx: Parse comma after colon tokens specially Otherwise the comma is treated as plain text by ParseContent. $<STREQUAL:,> should be valid and true. $<STREQUAL:,something> should be valid and false. $<STREQUAL:,,> should be non-valid as it is 3 parameters. $<STREQUAL:something,,> should be non-valid as it is 3 parameters. Additionally, this allows reporting the correct error for other expressions. For example $<TARGET_PROPERTY:,> should be invalid because it has an empty target and empty property. It shouldn't attempt to read the property ',' on the 'implicit this' target.
2012-10-04 02:34:03 +04:00
run_cmake(BadStrEqual)
Genex: Ensure that $<0:...> has a parameter.
2012-11-27 01:43:13 +04:00
run_cmake(BadZero)
Add the TARGET_NAME generator expression. It will be used as a preprocessing marker.
2012-12-10 14:33:23 +04:00
run_cmake(BadTargetName)
Tests: Add case for rejecting $<TARGET_FILE:...> on an INTERFACE library Add an explicit test for this existing error. We already cover it for an OBJECT library but INTERFACE libraries are not allowed either.
2015-05-26 18:51:34 +03:00
run_cmake(BadTargetTypeInterface)
Genex: Reject $<TARGET_FILE:...> for object libraries (#14532) Teach the cmGeneratorExpressionEvaluator filesystem artifact logic to reject OBJECT_LIBRARY targets since they have no main artifact. Without the explicit rejection evaluation falls through to an internal CMake error message in cmTarget::GetOutputInfo. Extend the RunCMake.GeneratorExpression test to cover these cases.
2013-11-01 18:14:47 +04:00
run_cmake(BadTargetTypeObject)
Make it an error for INSTALL_PREFIX to be evaluated. An empty string is not likely going to produce expected results in any evaluation context. It is replaced by preprocessing currently.
2013-01-30 20:49:47 +04:00
run_cmake(BadInstallPrefix)
Genex: Add a SHELL_PATH expression Some commands on Windows do not understand forward slash paths and require backslashes. In order to help projects generate shell invocations of such commands, provide a generator expression to convert paths to the shell-preferred path format for the current generator. This will allow custom commands to generate paths the same way CMake does for compiler command invocations.
2015-09-24 13:33:01 +03:00
run_cmake(BadSHELL_PATH)
Genex: Use case-sensitive comparison for COMPILER_ID.
2013-12-26 18:59:55 +04:00
run_cmake(CMP0044-WARN)
Genex: Clarify error message on use with non-binary targets (#14899).
2014-05-29 00:02:57 +04:00
run_cmake(NonValidTarget-C_COMPILER_ID)
run_cmake(NonValidTarget-CXX_COMPILER_ID)
run_cmake(NonValidTarget-C_COMPILER_VERSION)
run_cmake(NonValidTarget-CXX_COMPILER_VERSION)
run_cmake(NonValidTarget-TARGET_PROPERTY)
run_cmake(NonValidTarget-TARGET_POLICY)
Genex: Add a COMPILE_LANGUAGE generator expression.
2015-02-22 19:43:13 +03:00
run_cmake(COMPILE_LANGUAGE-add_custom_target)
run_cmake(COMPILE_LANGUAGE-add_custom_command)
run_cmake(COMPILE_LANGUAGE-install)
run_cmake(COMPILE_LANGUAGE-target_sources)
run_cmake(COMPILE_LANGUAGE-add_executable)
run_cmake(COMPILE_LANGUAGE-add_library)
run_cmake(COMPILE_LANGUAGE-add_test)
Genex: Enable use of COMPILE_LANGUAGE for compile options. Follow-ups will allow the use of the generator expression for compile definitions and include directories for non-IDE generators.
2014-11-26 00:47:44 +03:00
run_cmake(COMPILE_LANGUAGE-unknown-lang)
Add generator expression support to OUTPUT_DIRECTORY target properties If {ARCHIVE,LIBRARY,RUNTIME}_OUTPUT_DIRECTORY is set with a genex then do not add the per-config subdirectory on multi-config generators. This will allow projects to use $<CONFIG> to place the per-config part of the directory path somewhere other than the end.
2015-08-11 22:19:03 +03:00
run_cmake(TARGET_FILE-recursion)
cmGeneratorTarget: Avoid recursion in GetOutputName method Since support for generator expressions was added to OUTPUT_NAME it is possible for project code to cause recursion in this method by using a $<TARGET_FILE> genex. Detect and reject such cases.
2015-08-14 23:35:58 +03:00
run_cmake(OUTPUT_NAME-recursion)
Fix crash on $<TARGET_PROPERTY:...,LOCATION> genex (#16134) Policy CMP0026 deprecated the LOCATION property, and we have long provided a $<TARGET_FILE:...> generator expression. However, if a project tries to use $<TARGET_PROPERTY:...,LOCATION> we should at least not crash. The compatibility implementation of the LOCATION property uses cmGlobalGenerator::CreateGenerationObjects to create the structures needed to evaluate the property before generation starts. The implementation assumed that accessing the property could only be done during configuration (via the typical get_property command use case). The $<TARGET_PROPERTY:...,LOCATION> genex causes the LOCATION property to be accessed during generation. Calling CreateGenerationObjects during generation blows away all the objects currently being used for generation and is not safe. Add a condition to call it only when configuration is not finished.
2016-06-02 17:57:10 +03:00
run_cmake(TARGET_PROPERTY-LOCATION)
Genex: Diagnose invalid LINK_ONLY usage instead of crashing When `$<LINK_ONLY:...>` is used outside of linking we may evaluate it without a `dagChecker`. Do not dereference the NULL pointer and issue a diagnostic instead. Closes: #16287
2016-09-05 16:04:30 +03:00
run_cmake(LINK_ONLY-not-linking)
Genex: Implement generator expressions for target PDB files.
2014-07-25 00:18:21 +04:00
Reject TARGET_PDB_FILE for imported targets instead of crashing Reported-by: Justin Borodinsky <justin.borodinsky@gmail.com>
2015-08-03 22:28:41 +03:00
run_cmake(ImportedTarget-TARGET_PDB_FILE)
Genex: Implement generator expressions for target PDB files.
2014-07-25 00:18:21 +04:00
if(LINKER_SUPPORTS_PDB)
run_cmake(NonValidTarget-TARGET_PDB_FILE)
run_cmake(ValidTarget-TARGET_PDB_FILE)
else()
run_cmake(NonValidCompiler-TARGET_PDB_FILE)
endif()