summaryrefslogtreecommitdiffstats
path: root/Tests/CompileDefinitions
Commit message (Collapse)AuthorAgeFilesLines
* Genex: Do not consider 'head' when evaluating build propertiesBrad King2014-08-062-0/+15
| | | | | | | | | | | | When $<TARGET_PROPERTY> names a build property like COMPILE_DEFINITIONS but not the usage requirement (INTERFACE_) version of it, the value should be that used to build the target. It should not be influenced by a dependent 'head' target like usage requirements are. Extend the CompileDefinitions test with a case covering the corrected behavior. Reviewed-by: Stephen Kelly <steveire@gmail.com>
* cmTarget: Deprecate COMPILE_DEFINITIONS_ properties with a policy.Stephen Kelly2014-01-082-0/+7
|
* Remove the LINK_LANGUAGE generator expression.Stephen Kelly2013-07-243-9/+18
| | | | | | | | | | | It accepted an optional argument to test for equality, but no way to get the linker language of a particular target. TARGET_PROPERTY provides this flexibility and STREQUAL provides the necessary API for equality test. Extend the CompileDefinitions test to cover accessing the property of another target.
* Tests/CompileDefinitions: Avoid spaces in defines on VS 6Stephen Kelly2013-05-244-4/+18
| | | | | | | | The VS 6 IDE does not like spaces in definition values so CMake drops them and warns. The Tests/CompileDefinitions test C code that looks for the dropped definitions already knows to skip them, but CMake still warns. Silence the warnings by avoiding such values in the first place on VS 6.
* Add $<LINK_LANGUAGE> generator expressionStephen Kelly2013-05-245-0/+92
| | | | | | They can't be used when evaluating link libraries, but they can be used for include directories and compile definitions. Later they can be used for compile options.
* Add the JOIN generator expression.Stephen Kelly2013-05-162-3/+23
| | | | | | This generator expression joins a list with a separator. The separator may contain arbitrary content, such as commas, which is ordinarily a delimiter in the generator expression syntax.
* Test evaluation of per-config COMPILE_DEFINITIONS (#14037)Brad King2013-03-256-3/+92
| | | | | Teach the CompileDefinitions test to cover evaluation of config-specific generator expressions.
* GenEx: Test the use of generator expressions to generate lists.Stephen Kelly2012-10-172-0/+10
| | | | | | We can't test this in the GeneratorExpression unit test because the ';' chars are processed specically by the CMake function argument parser.
* Process generator expressions in the COMPILE_DEFINITIONS target property.Stephen Kelly2012-09-282-0/+15
|
* Rename files from main.cpp to more meaningful names.Stephen Kelly2012-08-225-5/+5
| | | | | | Because the main file for the dummy-executable and the actual compile test were both called main.cpp, they were overwriting each other during in-source builds.
* Fix the test setting COMPILE_DEFINITIONS target propertyStephen Kelly2012-08-211-1/+1
|
* Fix CompileDefinitions test on Visual Studio.Stephen Kelly2012-08-212-1/+10
| | | | Avoid testing unsupported spaces in define values.
* Don't duplicate -D defines sent to the compiler.Stephen Kelly2012-08-205-0/+70
There is no need to do so. Be consistent with include directories and ensure uniqueness. This requires changing the API of the cmLocalGenerator::AppendDefines method, and changing the generators to match. The test unfortunately can't test for uniqueness, but it at least verifies that nothing gets lost.
generated by cgit v0.12 at 2024-12-26 07:38:20 (GMT)