summaryrefslogtreecommitdiffstats
path: root/Tests
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'custom-command-expand-empty' into release-3.11Brad King2018-05-142-0/+2
|\ | | | | | | Merge-request: !2074
| * add_custom_{command,target}: Fix crash on empty expanded commandBrad King2018-05-142-0/+2
| | | | | | | | | | | | | | | | | | | | | | Our custom command generation logic assumes that all command lines have at least `argv0`. In `add_custom_{command,target}` we already check that at least a `COMMAND` was given, but using `COMMAND_EXPAND_LISTS` in combination with a generator expression that expands to an empty string may produce an empty command line. In this case simply add an empty string as a command to maintain our internal invariant. Fixes: #17993
* | add_library: Restore error on alias of non-global imported targetBrad King2018-05-101-2/+8
|/ | | | | | | | | | | In commit v3.11.0-rc1~433^2~1 (Add support for IMPORTED GLOBAL targets to be aliased, 2017-09-14) we accidentally dropped the error on calling `add_library` to alias an imported target that is not globally visible. The `add_executable` command's equivalent check was properly updated. Restore the check in `add_library` with the same update. Also fix the test case accordingly. Fixes: #17982
* Merge branch 'implicit-lib-gcceh-file' into release-3.11Brad King2018-04-161-0/+6
|\ | | | | | | Merge-request: !1967
| * Exclude "libgcc_eh" library files from implicit link librariesBrad King2018-04-161-0/+6
| | | | | | | | | | | | | | | | Extend the fix in commit v3.9.6~1^2 (Restore exclusion of "gcc_eh" from implicit link libraries, 2017-11-07) to also exclude `gcc_eh` libraries referenced by absolute path to the library file. Issue: #17436
* | Merge branch 'backport-fix-explicit-CMakeLists.txt' into release-3.11Brad King2018-04-136-0/+55
|\ \ | | | | | | | | | Merge-request: !1959
| * | Restore support for explicitly referenced CMakeLists.txt sourcesBrad King2018-04-136-0/+55
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit v3.11.0-rc1~467^2 (VS,Xcode: Add CMakeLists.txt sources without mutating targets, 2017-10-18) we do not add `CMakeLists.txt` to target sources but instead generate references to them directly. This broke projects that explicitly specify their `CMakeLists.txt` file as a source file because the explicit entry is no longer consolidated with the generated one. Teach the relevant generators to avoid duplicating `CMakeLists.txt` source references and add test cases. Fixes: #17828
* | Merge branch 'cpack-trace-nullptr' into release-3.11Brad King2018-04-104-0/+13
|\ \ | | | | | | | | | Merge-request: !1950
| * | CPack: Fix crash on invalid generator nameBrad King2018-04-104-0/+13
| |/ | | | | | | | | | | | | | | In commit v3.11.0-rc1~68^2 (CPack: accept --trace and --trace-expand, 2017-12-09) a nullptr dereference was added that occurs when `cpack -G NotAGenerator` is invoked. Add the needed condition. Fixes: #17900
* | Fix crash with --trace-expand --warn-uninitialized togetherR2RT2018-04-093-0/+10
|/ | | | | | | | Some code paths in `ExpandVariablesInString{New,Old}` were not checking the `filename` parameter for a null pointer, but this can happen when using the above flags together. Add the checks and a test case. Fixes: #17896
* Revert "Remove CTestTestfile.cmake when BUILD_TESTING is OFF"Brad King2018-03-264-0/+14
| | | | | | | | | | | | | Revert commit v3.8.0-rc1~305^2 (Remove CTestTestfile.cmake when BUILD_TESTING is OFF, 2016-11-14) again. We reverted it once in commit v3.8.0-rc3~22^2 (Revert "Remove CTestTestfile.cmake when BUILD_TESTING is OFF", 2017-03-06) but it was accidentally restored by commit v3.11.0-rc1~387^2 (server: add "ctestInfo" request to get test info, 2017-10-25), perhaps due to conflict resolution during rebase. We cannot remove `CTestTestfile.cmake` when testing is off because it breaks projects that never enable testing but create their own `CTestTestfile.cmake` manually instead. Revert the change again and add a test case.
* Merge branch 'intel-initializer-list' into release-3.11Brad King2018-03-161-0/+6
|\ | | | | | | Merge-request: !1855
| * Features: Record initializer list support for Intel 14 and aboveBrad King2018-03-161-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Features recorded by commit v3.6.0-rc1~120^2~5 (Features: Record standards and features for Intel C++ on UNIX, 2016-04-28) for the Intel compiler left out initializer list support because our test case in `Tests/CompileFeatures/cxx_generalized_initializers.cpp` caused an internal compiler error. It turns out this is because the Intel compiler asserts the `initializer_list` constructor signatures to verify that they match its own `<initializer_list>` header. It was our dummy implementation used to test the language feature without any headers that caused the ICE. Revise it to use a constructor signature accepted by the Intel compiler. Fixes: #17829
* | Merge branch 'gtest_discover_tests_timeout' into release-3.11Brad King2018-03-1613-10/+113
|\ \ | | | | | | | | | Merge-request: !1851
| * | GoogleTest: Rename TIMEOUT parameter to avoid clashCraig Scott2018-03-1513-10/+113
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In gtest_discover_tests(), the TIMEOUT keyword was making it impossible to set the TIMEOUT test property via the PROPERTIES keyword. This would be a frequent case, but it doesn't complain and instead silently does something different to what would normally be expected. The TIMEOUT keyword has been renamed to DISCOVERY_TIMEOUT, thereby removing the clash. This is a breaking change. 3.10.1 and 3.10.2 were the only versions that supported the TIMEOUT keyword and uses of it were likely not working as intended. Fixes: #17801
| * | Merge branch 'automoc-apple-framework' into release-3.10Brad King2017-12-078-0/+162
| |\ \ | | | | | | | | | | | | Merge-request: !1561
* | \ \ Merge branch 'genex-COMPILE_LANGUAGE-system-include' into release-3.11Brad King2018-03-131-1/+3
|\ \ \ \ | | | | | | | | | | | | | | | Merge-request: !1844
| * | | | Genex: Fix COMPILE_LANGUAGE propagation through try_compileBrad King2018-03-121-8/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When evaluating include directories during export to a `try_compile` test project, thread the compile language through to the generator expression evaluator so it can support `$<COMPILE_LANGUAGE:...>`. Issue: #17811
| * | | | Genex: Fix COMPILE_LANGUAGE in SYSTEM include directoriesBrad King2018-03-121-0/+7
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When evaluating `INTERFACE_SYSTEM_INCLUDE_DIRECTORIES`, or evaluating `INTERFACE_INCLUDE_DIRECTORIES` on an imported target, thread the compile language through to the generator expression evaluator so that it can support `$<COMPILE_LANGUAGE:...>`. Fixes: #17811
* | | | ExternalProject: Fix cache generation when last args ends with "-NOTFOUND"Jean-Christophe Fillion-Robin2018-03-124-2/+22
|/ / /
* | | Merge branch 'unixtimefix' into release-3.11Brad King2018-02-262-4/+4
|\ \ \ | | | | | | | | | | | | Merge-request: !1800
| * | | Tests: Fix TIMESTAMP-UnixTime test under SOURCE_DATE_EPOCH=1Bernhard M. Wiedemann2018-02-262-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The test was expecting timestamps on day 1 in 1970 to start at 86400 but they actually started at 0. This worked without `SOURCE_DATE_EPOCH=1` because after 1972, leap days compensated the offset. Fixes: #17762
* | | | Xcode: Generate ZERO_CHECK generator target only onceGregor Jasny2018-02-224-0/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In case CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY has been enabled generate only the root-level ZERO_CHECK target so targets in subdirectories pick up the root generator target of ZERO_CHECK. For the case that CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY is not enabled more investigation and a proper and final fix is still needed. Issue: 14297
* | | | Merge branch 'test-CompileFeatures-c11-range' into release-3.11Brad King2018-02-211-1/+1
|\ \ \ \ | | | | | | | | | | | | | | | Merge-request: !1785
| * | | | Tests: Make CompileFeatures C dialect check consistent with implBrad King2018-02-211-1/+1
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | `Modules/CMakeCCompilerId.c.in` will report the C dialect as 11 whenever `__STDC_VERSION__` indicates *at least* C 11. Make the test consistent with this. We already do this for the C++ case. Fixes: #17740
* | | | Android.mk: Fix export of static libraries with PRIVATE dependenciesBrad King2018-02-141-1/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | The `LINK_ONLY` generator expression is used to represent private dependencies of static libraries in their `INTERFACE_LINK_LIBRARIES` property value. Fix evaluation of generator expressions during export to support the `LINK_ONLY` genex. Extend the RunCMake.AndroidMK test with a case for this.
* | | Tests: Add missing error check in CudaOnly.GPUDebugFlagBrad King2018-02-011-0/+5
| | | | | | | | | | | | If `cudaMallocManaged` fails then later use of `has_debug` is not valid.
* | | Merge topic 'msvc_cuda_files_use_consistent_obj_names'Brad King2018-01-316-23/+37
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | fa583869 CUDA: Use MSVC default pattern for naming object files Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !1722
| * | | CUDA: Use MSVC default pattern for naming object filesRobert Maynard2018-01-306-23/+37
| | | | | | | | | | | | | | | | | | | | The default that CUDA uses causes failures when you try to embed CUDA obj's into another target.
* | | | Merge topic 'source_group-TREE-args'Brad King2018-01-314-4/+21
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | 365e02e7 source_group: Fix TREE argument parsing Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !1713
| * | | source_group: Fix TREE argument parsingMateusz Janek2018-01-304-4/+21
| | | | | | | | | | | | | | | | Fixes: #17581
* | | | Merge topic 'ctest_start_function_scope'Brad King2018-01-293-1/+12
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | 13347740 Help: add release notes, documentation for CTEST_RUN_CURRENT_SCRIPT behavior 74092d92 cmCTestScriptHandler: Add new field ShouldRunCurrentScript Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !1703
| * | | cmCTestScriptHandler: Add new field ShouldRunCurrentScriptKyle Edwards2018-01-263-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is to avoid scope issues with CTEST_RUN_CURRENT_SCRIPT. If ctest_start() is called within a function scope, the value of CTEST_RUN_CURRENT_SCRIPT that it sets doesn't make it to the global scope. With this change, ctest_start() no longer sets CTEST_RUN_CURRENT_SCRIPT, and instead sets a field directly in cmCTestScriptHandler. The old behavior of CTEST_RUN_CURRENT_SCRIPT has also been kept for projects and tests that rely on setting it.
* | | | Tests: Speed up RunCMake.TargetPropertyGeneratorExpressionsBrad King2018-01-2562-241/+135
| | | | | | | | | | | | | | | | Consolidate similar test cases.
* | | | Tests: Speed up RunCMake.GeneratorExpressionBrad King2018-01-2525-71/+30
|/ / / | | | | | | | | | Avoid enabling languages in cases that do not need them.
* | | Merge topic 'RemoveKDevelop3'Brad King2018-01-252-3/+2
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 551bd0b3 Generators: adjust error message for the removed KDevelop3 generator 9198e6a2 Generators: remove KDevelop3 generator Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !1688
| * | | Generators: remove KDevelop3 generatorAlex Neundorf2018-01-242-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The last KDevelop3 release was many years ago, in 2008 I think. I haven't seen or read about anybody using KDevelop 3 since a long time, so I think it can safely be removed from CMake. KDevelop 4 (first released in 2010) has its own proper CMake support now, independent from this generator. Alex
* | | | Merge topic 'sourceFile-new-properties'Brad King2018-01-2526-48/+139
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 04483111 sourceFile properties: add property INCLUDE_DIRECTORIES 3073bd1f VisualStudio generators: refactoring 78b1c2e0 sourceFile properties: add property COMPILE_OPTIONS 3f935e69 LocalGenerator: refactoring Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !1596
| * | | | sourceFile properties: add property INCLUDE_DIRECTORIESMarc Chevrier2018-01-2422-2/+113
| | | | |
| * | | | sourceFile properties: add property COMPILE_OPTIONSMarc Chevrier2018-01-235-48/+28
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | Add the support of per-source property COMPILE_OPTIONS, including generator expressions support. Related: #17507
* | | | Merge topic 'fix-include_regular_expression-subdir'Brad King2018-01-254-0/+9
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2d64f9f0 include_regular_expression: Fix propagation to subdirectories Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !1690
| * | | | include_regular_expression: Fix propagation to subdirectoriesBrad King2018-01-244-0/+9
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Refactoring in commit v3.4.0-rc1~321^2 (cmMakefile: Remove special handling of INCLUDE_REGULAR_EXPRESSION, 2015-04-04) accidentally broke propagation of the include regex to subdirectories. Refactoring in commit v3.5.0-rc1~319^2~1 (cmState: Initialize properties immediately, 2015-10-07) moved maintenance of this value from `cmMakefile` to `cmStateSnapshot`. Restore propagation of the `INCLUDE_REGULAR_EXPRESSION` to subdirectories and add a test to cover it. Fixes: #17676
* | | | Merge topic 'GenerateExportHeader-include-guard'Brad King2018-01-2419-14/+46
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | b1ae9aaf GenerateExportHeader: add release notes, tests for include guard changes f4082b0e GenerateExportHeader: add INCLUDE_GUARD_NAME option Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !1643
| * | | | GenerateExportHeader: add release notes, tests for include guard changesKyle Edwards2018-01-2319-14/+46
| |/ / /
* | | | Merge topic 'UseJava-native-headers-generation'Brad King2018-01-247-16/+129
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | 4829ea23 add_jar: add option GENERATE_NATIVE_HEADERS Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !1675
| * | | add_jar: add option GENERATE_NATIVE_HEADERSMarc Chevrier2018-01-227-16/+129
| | | |
* | | | Merge topic 'autogen-first-line-fix'Brad King2018-01-2217-48/+198
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | b4e6911b Autogen: Tests: Extend AUTOUIC include patterns test ff91a5d5 Autogen: Tests: Extend AUTOMOC include patterns test a1d491ca Autogen: AUTOMOC/UIC fix for moc/uic include on the first line Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !1670
| * | | | Autogen: Tests: Extend AUTOUIC include patterns testSebastian Holtermann2018-01-1911-46/+116
| | | | |
| * | | | Autogen: Tests: Extend AUTOMOC include patterns testSebastian Holtermann2018-01-186-2/+82
| |/ / /
* | | | Merge topic 'boost-optional-components'Brad King2018-01-224-1/+66
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2557cad5 FindBoost: support OPTIONAL_COMPONENTS Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Paul "TBBle" Hampson <paul.hampson@pobox.com> Merge-request: !1660
generated by cgit v0.12 at 2025-01-13 00:51:59 (GMT)