summaryrefslogtreecommitdiffstats
path: root/Tests
Commit message (Collapse)AuthorAgeFilesLines
* Xcode: ensure framework with custom output directory can be consumedMarc Chevrier2022-10-142-0/+27
| | | | Fixes: #24046
* Merge topic 'flang-implicit-link-info' into release-3.25Brad King2022-10-125-2/+48
|\ | | | | | | | | | | | | | | 0301779e85 LLVMFlang: Add support for mixed-language linking with Fortran Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7781
| * LLVMFlang: Add support for mixed-language linking with FortranBrad King2022-10-115-2/+48
| | | | | | | | | | | | | | | | | | Parse implicit link information for this compiler to support mixed-language linking. This was missed by commit 85749766df (LLVMFlang: Add support for LLVM Flang, 2021-07-07, v3.24.0-rc1~86^2). Also activate mixed-language test cases that would have caught this. Issue: #22387
* | Merge topic 'test-RunCMake.install'Brad King2022-10-111-1/+1
|\ \ | | | | | | | | | | | | | | | | | | e73470991f Tests: Loosen RunCMake.install directory symlink expected output Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7775
| * | Tests: Loosen RunCMake.install directory symlink expected outputBrad King2022-10-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | The case added by commit 85f01a1ec2 (file(INSTALL): Improve formatting of symlink creation error, 2022-10-06) may print `Up-to-date:` or `Installing:` for the file inside a symlinked directory based on filesystem timestamp granularity. Since that output is not what the test intends to cover, simply accept either possibility.
* | | Merge topic 'verify-header-sets-iwyu'Brad King2022-10-101-1/+1
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6942234bf5 VERIFY_INTERFACE_HEADER_SETS: Add IWYU pragma: associated to verification file Acked-by: Kitware Robot <kwrobot@kitware.com> Tested-by: buildbot <buildbot@kitware.com> Merge-request: !7762
| * | | VERIFY_INTERFACE_HEADER_SETS: Add IWYU pragma: associated to verification fileDaniel Hannon2022-10-071-1/+1
| | | |
* | | | Merge topic 'cuda_sanitizer_false_positives'Brad King2022-10-101-0/+9
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | 59fcbba65e ctest_memcheck: ignore false-positives in CUDA's compute-sanitizer Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7760
| * | | ctest_memcheck: ignore false-positives in CUDA's compute-sanitizerTobias Ribizel2022-10-071-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a list of false-positive messages from CUDA's compute-sanitizer to the CTest memcheck. Fixes: #24001
* | | | Tests: Run CheckSourceTree test using just-built CMakeBrad King2022-10-081-3/+3
| |/ / |/| | | | | | | | | | | | | | Update the change from commit 8d453ee751 (Tests: Improve CheckSourceTree test, 2022-10-05) to drive the test script using the tested CMake instead of the host CMake, following the convention of other tests.
* | | Merge topic 'clang-tidy-prefer-p-option'Brad King2022-10-073-0/+18
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 3f4e0839c4 clang-tidy: Don't append compiler commands if using -p Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7753
| * | | clang-tidy: Don't append compiler commands if using -pCraig Scott2022-10-073-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the -p option is given to clang-tidy, it doesn't need the compile command line to be appended. It can get everything it needs from the compile_commands.json file in the directory specified with the -p option. When the compiler being used is not the system default compiler, clang-tidy has been observed to pick up the wrong headers when the compiler command line is given, but not if only the -p option is used. Therefore, don't append the compiler command line if -p is present in the <LANG>_CLANG_TIDY target property. Fixes: #24017
* | | | Merge topic 'improve-symlink-error-reporting'Brad King2022-10-075-0/+40
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 569fb1893e file(INSTALL): Report "Installing:" for a symlink to a directory 1461ae4933 file(INSTALL): Clarify symlink vs dir conflict errors 85f01a1ec2 file(INSTALL): Improve formatting of symlink creation error aba48bd6ac cmSystemTools: Provide quiet link creation methods Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7706
| * | | | file(INSTALL): Report "Installing:" for a symlink to a directoryJohn Parent2022-10-061-1/+1
| | | | |
| * | | | file(INSTALL): Clarify symlink vs dir conflict errorsJohn Parent2022-10-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Clarify error reporting in scenario creating a symlink where a directory previously exists.
| * | | | file(INSTALL): Improve formatting of symlink creation errorBrad King2022-10-065-0/+40
| | |/ / | |/| | | | | | | | | | Avoid printing two error messages. Format paths without wrapping.
* | | | Merge topic 'automoc-skip-pch'Brad King2022-10-072-0/+33
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 681714ce20 AUTOMOC: Skip PCH when all sources files skip the PCH file too Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7759
| * | | | AUTOMOC: Skip PCH when all sources files skip the PCH file tooCristian Adam2022-10-062-0/+33
| |/ / / | | | | | | | | | | | | Fixes: #23464
* | | | Tests: Move TryCompile check module cases to RunCMake.Check*Brad King2022-10-0614-144/+226
| | | | | | | | | | | | | | | | The latter already have similar checks for similar modules.
* | | | Tests: Clarify RunCMake.Check* case namesBrad King2022-10-0634-30/+30
|/ / / | | | | | | | | | | | | | | | Cases for `CheckSource{Compiles,Runs}` and `Check{Compiler,Linker}Flag` cover the modules with the language as a parameter, not the language-specific modules.
* | | Merge topic 'try_compile-more-debug-logging'Brad King2022-10-064-1/+34
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7e6b2a92a0 try_compile: Report build dir with --debug-trycompile cbf3252975 Tests: Remove stray debugging flag from RunCMake.CheckCompilerFlag case Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7746
| * | | try_compile: Report build dir with --debug-trycompileMatthew Woehlke2022-10-063-0/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When `--debug-trycompile` is enabled, issue a log (with trace) for every `try_compile` noting what directory is being used for the compilation. This will make it easier to find the corresponding artifacts. Closes: #24022
| * | | Tests: Remove stray debugging flag from RunCMake.CheckCompilerFlag caseBrad King2022-10-051-1/+1
| |/ /
* | | Tests: Improve CheckSourceTree testBrad King2022-10-055-380/+36
|/ / | | | | | | | | | | | | | | Re-implement the test using simpler approach. Enable it only when doing an out-of-source build with a `.git` source. Run it last, serially. Re-use the `git` tool found for version computation. Print the output from `git status` without modification. Rely on `.gitignore` instead of filtering out paths ourselves.
* | Merge topic 'ci-intel-compiler'Brad King2022-10-041-0/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | f391c1c269 gitlab-ci: add jobs testing Intel 2022.2.0 compilers on Linux 29e45a94b0 Tests: Teach RunCMake to ignore Intel Classic compiler deprecation warnings Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7742
| * | Tests: Teach RunCMake to ignore Intel Classic compiler deprecation warningsBrad King2022-10-031-0/+1
| | |
* | | Merge topic 'xcode-ios-objects'Brad King2022-10-042-0/+30
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 25630863ea Tests: Add case covering XCODE_EMIT_EFFECTIVE_PLATFORM_NAME=OFF for iOS Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7740
| * | | Tests: Add case covering XCODE_EMIT_EFFECTIVE_PLATFORM_NAME=OFF for iOSBrad King2022-10-032-0/+30
| |/ / | | | | | | | | | | | | | | | | | | | | | This use case was fixed by commit a7fb4bc475 (Xcode: Set build product locations using CONFIGURATION_BUILD_DIR, 2022-09-28). Add a test to verify the fix. Fixes: #23970
* | | Merge topic 'try_compile-rename-source_from_arg'Brad King2022-10-047-11/+11
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 0f28653ba9 try_compile: Rename SOURCE_FROM_ARG -> SOURCE_FROM_CONTENT Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7733
| * | try_compile: Rename SOURCE_FROM_ARG -> SOURCE_FROM_CONTENTMatthew Woehlke2022-09-307-11/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | Change the SOURCE_FROM_ARG keyword to try_compile to SOURCE_FROM_CONTENT (which we can do because it was recently added and hasn't been in a release yet). The new name should be clearer as to what it does, and also more consistent with the CONTENT arguments to some other commands. Also, fix a typo in an error message.
* | | Merge topic 'ci-xcode-14.0'Brad King2022-10-035-29/+53
|\ \ \ | | |/ | |/| | | | | | | | | | | | | | | | | | | 9cdf4c9be4 gitlab-ci: update macOS jobs to use Xcode 14.0 5d2c2b2558 Tests: Update RunCMake.XcodeProject iOS cases for Xcode 14.0 12c6fec6b4 Xcode: Drop CMAKE_INTDIR= definition in Swift targets Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7732
| * | Tests: Update RunCMake.XcodeProject iOS cases for Xcode 14.0Brad King2022-09-305-29/+53
| | | | | | | | | | | | Issue: #24011
* | | Merge topic 'xcode-build-layout'Brad King2022-09-304-0/+11
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | d0a6ebf57b Xcode: Fix "clean" operation under the "new build system" dc5fc898f6 Xcode: Set object file locations using TARGET_TEMP_DIR a7fb4bc475 Xcode: Set build product locations using CONFIGURATION_BUILD_DIR 6883b82124 cmGlobalXCodeGenerator: Remove unused local variable settings Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7730
| * | | Xcode: Fix "clean" operation under the "new build system"Brad King2022-09-294-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously we set `SYMROOT` to tell Xcode where to place the build products. However, the "clean" operation in the Xcode "new build system" expects that only Xcode creates the `SYMROOT` directory or contents inside it. Since we create that directory, "clean" fails. We now explicitly set `CONFIGURATION_BUILD_DIR` and `TARGET_TEMP_DIR` instead of letting Xcode compute their values from `SYMROOT`, so we no longer need to set the latter. Drop the now-unnecessary `SYMROOT`. Fixes: #22550
* | | | Tests: Test more CMakeTest*Compiler.cmake fallbacksBrad King2022-09-2910-0/+46
| |_|/ |/| | | | | | | | | | | Extend the test added by commit f891a75d5c (Tests: Test CMakeTest*Compiler.cmake fallbacks, 2022-09-27) to cover more languages.
* | | Merge topic 'try_compile-no-cache'Brad King2022-09-291-0/+52
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 09b3051524 try_compile: Add NO_CACHE option (also try_run) Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7723
| * | | try_compile: Add NO_CACHE option (also try_run)Matthew Woehlke2022-09-281-0/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add NO_CACHE option to try_compile and try_run, which places the results in regular, rather than cache, variables. Issue: #22799
* | | | Merge topic 'compiler-tests'Brad King2022-09-2911-0/+36
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | f891a75d5c Tests: Test CMakeTest*Compiler.cmake fallbacks Acked-by: Kitware Robot <kwrobot@kitware.com> Tested-by: buildbot <buildbot@kitware.com> Merge-request: !7722
| * | | Tests: Test CMakeTest*Compiler.cmake fallbacksMatthew Woehlke2022-09-2811-0/+36
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | Add tests that explicitly test the fallback tests of the modules which test for a functional [Obj]C[xx] compiler, bypassing the ABI tests. Due to the ABI test short-circuiting added by commit 1d21dd0f7c (enable_language: Assume compiler works if ABI detection compiles, 2020-05-25, v3.18.0-rc1~93^2), this logic is likely not getting tested otherwise.
* | | Merge topic 'vs11-deprecate'Brad King2022-09-286-1/+20
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6c1337cb79 Deprecate Visual Studio 11 2012 generator 5faf145a5b Tests: Drop unused files from RunCMake.CommandLine Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7720
| * | | Deprecate Visual Studio 11 2012 generatorBrad King2022-09-276-1/+20
| | | | | | | | | | | | | | | | | | | | Update documentation to mark the generator deprecated. Add a warning at the end of generation plus an option to turn off the warning.
| * | | Tests: Drop unused files from RunCMake.CommandLineBrad King2022-09-272-0/+0
| |/ / | | | | | | | | | | | | Remove files missed by commit 8d6f015d59 (Drop Visual Studio 10 2010 generator, 2022-09-26).
* | | Merge topic 'cmake-presets-workflow'Brad King2022-09-2850-0/+514
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | 374d82bbcd cmake: Add --workflow mode e316812884 CMakePresets.json: Add workflow presets to schema Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7711
| * | cmake: Add --workflow modeKyle Edwards2022-09-2750-0/+514
| | | | | | | | | | | | Fixes: #23118
* | | Merge topic 'remove-vs10-generator'Brad King2022-09-274-24/+1
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 8d6f015d59 Drop Visual Studio 10 2010 generator Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7718
| * | | Drop Visual Studio 10 2010 generatorBrad King2022-09-264-24/+1
| |/ / | | | | | | | | | This generator has been deprecated since CMake 3.22. Remove it.
* | | Merge topic 'add_subdirectory_system'Brad King2022-09-2731-0/+118
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 2eb30a7036 add_subdirectory: Add SYSTEM option Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !7399
| * | | add_subdirectory: Add SYSTEM optionDa Quexian2022-09-2631-0/+118
| | | | | | | | | | | | | | | | | | | | Fixes: #22401 Signed-off-by: Da Quexian <daquexian566@gmail.com>
* | | | Merge topic 'ctest_ninja_full_output'Brad King2022-09-276-1/+43
|\ \ \ \ | |_|/ / |/| | / | | |/ | |/| | | | | | | | | | 65260d6c1e ctest: only report make-level errors when no others are found Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !7710
| * | ctest: only report make-level errors when no others are foundZack Galbreath2022-09-266-1/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit ab9ad2a6a0 (ctest: report make-level errors to CDash when using launchers, 2020-09-24, v3.19.0-rc1~84^2~1) we taught CTest to capture and report errors from the build command when using launchers. This had the unintended side effect of reporting a separate build error containing the full build output when the build command returns non-zero. To fix this problem, we now only report build command errors from CTest launchers when no other more specific build errors are found. Fixes: #23991
generated by cgit v0.12 at 2024-11-15 00:37:24 (GMT)