summaryrefslogtreecommitdiffstats
path: root/Modules
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'cuda_11' into release-3.19Brad King2020-11-231-4/+6
|\ | | | | | | | | | | | | | | 046e454fdd CUDA: Error if can't determine toolkit library root 440dc98b07 CUDA: Clang CUDA 11.1 support Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5525
| * CUDA: Error if can't determine toolkit library rootRaul Tambre2020-11-221-0/+2
| | | | | | | | | | | | | | Finding the toolkit is required for Clang and is assumed to have been correctly found by FindCUDAToolkit if the CUDA language is found. Error out early with an useful error instead of failing later on due to the path not being set.
| * CUDA: Clang CUDA 11.1 supportRaul Tambre2020-11-221-4/+4
| | | | | | | | | | | | | | | | | | version.txt is gone from CUDA 11.1 installations, but the rest is the same. Instead of looking for version.txt look for <CUDA path>/nvvm/libdevice, which is the main thing that Clang requires (though it also checks for the existence of bin and include). Fixes #21353.
* | Merge topic 'FindGTest-revert-no-release' into release-3.19Brad King2020-11-231-28/+12
|\ \ | |/ |/| | | | | | | | | 64dc4efc51 FindGTest: Revert "Allow either "Debug" or "Release" configurations." Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5520
| * FindGTest: Revert "Allow either "Debug" or "Release" configurations."Brad King2020-11-201-28/+12
| | | | | | | | | | | | | | | | | | | | | | Revert commit a064b18f85 (FindGTest: Allow either "Debug" or "Release" configurations., 2020-06-29, v3.19.0-rc1~584^2). If both configurations are found then `GTEST_LIBRARY` is populated in a way that breaks `__gtest_determine_library_type`, and the imported target is not created correctly. Fixes: #21473 Issue: #17799
* | Revert "specify language flag when source LANGUAGE property is set"Brad King2020-11-1912-24/+3
|/ | | | | | | | | | | | | | | | | | | | | | | | | Revert commit 74b1c9fc8e (Explicitly specify language flag when source LANGUAGE property is set, 2020-06-01, v3.19.0-rc1~722^2) and the lookup tables from its two immediate ancestors. The purpose of that change was to convert an explicit `LANGUAGE` source file property into an explicit language specification compiler flag like `-x c`. This seems reasonable since the property is documented as meaning "indicate what programming language the source file is". It is also needed to help compilers deal with non-standard source file extensions they don't recognize. However, some projects have been setting `LANGUAGE C` on `.S` assembler source files to mean "use the C compiler". Passing `-x c` for them breaks the build because the `.S` sources are not written in C. These projects should be updated to use `enable_language(ASM)`, for which CMake often chooses the C compiler as the assembler when using toolchains that support it (which would have to be the case for projects using the approach). Revert the change for now to preserve the old behavior for such projects. We can re-introduce it with a policy in a future version of CMake. Fixes: #21469 Issue: #14516, #20716
* CTest: Rename CudaMemcheck to CudaSanitizerTobias Ribizel2020-11-171-2/+2
|
* Merge topic 'qtifw-archivegen' into release-3.19Brad King2020-11-131-0/+10
|\ | | | | | | | | | | | | 5ab75dd7dd CPack/IFW: Locate the archivegen utility Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5503
| * CPack/IFW: Locate the archivegen utilityErlend Egeberg Aasland2020-11-121-0/+10
| | | | | | | | Fixes: #21427
* | Merge topic 'qtifw-4.0' into release-3.19Brad King2020-11-131-1/+2
|\ \ | | | | | | | | | | | | | | | | | | 63ae96a317 CPack/IFW: Add support for QtIFW 4.0 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5502
| * | CPack/IFW: Add support for QtIFW 4.0Erlend Egeberg Aasland2020-11-121-1/+2
| | | | | | | | | | | | | | | | | | | | | installerbase v4.0 segfaults on macOS if you pass `--framework-version`, so re-order flags to try `--version` first. Fixes: #21426
* | | Merge topic 'xcode-compiler-id-path' into release-3.19Brad King2020-11-134-4/+4
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | bcbae3f71e Xcode: Extract CMAKE_<LANG>_COMPILER from compiler id with multiple archs a070565a66 Merge branch 'FindRuby-restore-VENDORLIB_DIR' into release-3.18 3969c86b51 Merge branch 'cuda_vs_skip_computation' into release-3.18 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5506
| * | | Xcode: Extract CMAKE_<LANG>_COMPILER from compiler id with multiple archsBrad King2020-11-124-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When targeting a platform that supports multiple architectures, Xcode may choose to build all of them in our small compiler id project. Update the regex we use to extract the path to the compiler from the Xcode output to account for this. Fixes: #21425
* | | | Xcode: Default to arm64 arch on Apple Silicon hosts during compiler idBrad King2020-11-122-2/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit b6c60f14b6 (macOS: Default to arm64 architecture on Apple Silicon hosts, 2020-09-28, v3.19.0-rc1~63^2) we forgot to update the compiler id architecture selection added by commit 26673bf480 (Xcode: Explicitly specify default native architecture on macOS, 2020-07-16, v3.18.1~20^2). Issue: #21425
* | | | Merge topic 'FindRuby-vs-runtimes' into release-3.19Brad King2020-11-121-7/+13
|\ \ \ \ | |_|_|/ |/| | | | | | | | | | | | | | | | | | | d4a16427e2 FindRuby: Consider more VS runtime suffix combinations Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5486
| * | | FindRuby: Consider more VS runtime suffix combinationsSilvio Traversaro2020-11-111-7/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | These are needed to find recent Ruby versions for builds using recent VS versions. Fixes: #21066
* | | | Merge topic 'android-abi' into release-3.19Brad King2020-11-111-4/+13
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | a585b75df9 Android: Use NDK_KNOWN_DEVICE_ABI{32,64}S instead of NDK_DEFAULT_ABIS Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5488
| * | | Android: Use NDK_KNOWN_DEVICE_ABI{32,64}S instead of NDK_DEFAULT_ABISHaibo Huang2020-11-101-4/+13
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | Revise logic from commit 1ab574a0f4 (Android: Add support for NDK r22, 2020-10-07, v3.19.0-rc1~18^2) that loads ABI tables from the NDK. `NDK_DEFAULT_ABIS` means the abis to build by default. Use `NDK_KNOWN_DEVICE_ABI{32,64}S` instead. In practise they have never been different. Fix to make it more precise.
* | | FindPython{Interp,Libs}: Add support for version 3.10Miro Hrončok2020-11-092-2/+2
|/ / | | | | | | | | | | Extend the change from commit 23cd98a66a (FindPython: Add support of version 3.10, 2020-10-16, v3.19.0-rc2~25^2) to cover the legacy `FindPython{Interp,Libs}` modules too.
* | Merge topic 'apple-v4-tbd-file-arch-lookup' into release-3.19Brad King2020-11-061-3/+9
|\ \ | | | | | | | | | | | | | | | | | | 4c6797e03e Apple: Update SDK architecture detection for tbd file version 4 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5470
| * | Apple: Update SDK architecture detection for tbd file version 4Tor Arne Vestbø2020-11-051-3/+9
| | | | | | | | | | | | | | | | | | Extend the `.tbd` parsing from commit 170e598add (iOS: Fix detection of supported SDK architectures, 2020-04-16, v3.17.2~11^2) to support `.tbd` file version 4.
* | | Merge topic 'FindPostgreSQL-13' into release-3.19Brad King2020-11-061-1/+1
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | f3f09f1c96 FindPostgreSQL: support version 13 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5468
| * | | FindPostgreSQL: support version 13Pavel Cernohorsky2020-11-051-1/+1
| |/ /
* | | CTest: Add cuda-memcheck to Dart and CTest moduleTobias Ribizel2020-11-052-1/+3
|/ / | | | | | | Issue: #21388
* | cmake_path: remove new command from 3.19Marc Chevrier2020-11-031-3/+2
| | | | | | | | | | | | | | Defer adding this command until post-3.19 development so that it has more time to mature before being included in a release. Issue: #21385
* | Merge topic 'fix-cuda-qnx' into release-3.19Brad King2020-11-033-3/+7
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 0832516bec Help: Add 3.19 release note about CUDA support on QNX bcdd486bf7 CUDA: Enable support on QNX Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Raul Tambre <raul@tambre.ee> Merge-request: !5446
| * | CUDA: Enable support on QNXjanbernloehr2020-11-023-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes the following two issues with the CUDA support on QNX: * cuda target name is not derived correctly (should be `aarch64-qnx`). * linking `cudart` must not be linked against `rt`, `dl`, `pthread`. This enables to use cmake's native cuda support on QNX. Fixes: #21381
* | | Merge topic 'doc-cpack-pre-post-scripts' into release-3.19Craig Scott2020-11-031-16/+28
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | b77dfa441f Help: Clarify variables specifying scripts to execute during packaging Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Alex Turbov <i.zaufi@gmail.com> Merge-request: !5454
| * | | Help: Clarify variables specifying scripts to execute during packagingCraig Scott2020-11-031-16/+28
| | | | | | | | | | | | Relates: #19077
* | | | Merge topic 'FindBoost-config-mode' into release-3.19Brad King2020-11-021-2/+8
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | 685fa8bec0 FindBoost: Avoid leaking internal Boost_ROOT setting Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5445
| * | | FindBoost: Avoid leaking internal Boost_ROOT settingBrad King2020-10-301-2/+8
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | Since commit 4b2a61946f (FindBoost: Honor BOOST_ROOT when finding upstream BoostConfig, 2020-10-22, v3.19.0-rc2~14^2) we accidentally leak our internal setting of `Boost_ROOT`. Revise the logic to unset our temporary value. Fixes: #21379
* | | Merge topic 'CheckSourceRuns-compatibility' into release-3.19Brad King2020-10-305-1/+14
|\ \ \ | |/ / |/| | | | | | | | | | | | | | a524bf3aa7 CheckSourceRuns: do not fail on unrecognized arguments Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5426
| * | CheckSourceRuns: do not fail on unrecognized argumentsBen Boeckel2020-10-285-1/+14
| | | | | | | | | | | | | | | | | | | | | The old `check_X_source_runs` modules did not verify the arguments, so we cannot start doing it now. Downgrade the hard error introduced in commit 357e2ef429 (CheckSoureRuns: Add a unified way to check if a source runs, 2020-09-14) via !5223 into a noisy warning.
* | | Merge branch 'release-3.19' into FindRuby-restore-VENDORLIB_DIRBrad King2020-10-27181-2002/+3910
|\ \ \ | |/ / | | / | |/ |/|
| * Merge topic 'correct_msvc_cuda_flag_warning' into release-3.19Brad King2020-10-271-4/+11
| |\ | | | | | | | | | | | | | | | | | | 2b0d3c3524 CUDA: Use MSVC version to determine supported C++ standard levels Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5423
| | * CUDA: Use MSVC version to determine supported C++ standard levelsRobert Maynard2020-10-261-4/+11
| | | | | | | | | | | | Fixes: #21335
| * | Modules: Do not implicitly add new functions via old Check ModulesRobert Maynard2020-10-2621-354/+380
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The conversion of Check<Lang>CompilerFlag, SourceCompiles, and SourceRuns over to the new functions has the possibility of breaking projects that had functions with those existing names. To reduce the possibility of collisions we now have all the legacy code call functions that start with `cmake_`, and users will need to explicitly include the new modules to get the non-prefixed versions Fixes: #21359
| * | Merge topic 'FindBoost-config-mode' into release-3.19Brad King2020-10-261-1/+12
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4b2a61946f FindBoost: Honor BOOST_ROOT when finding upstream BoostConfig b32cb33275 FindBoost: Honor Boost_NO_SYSTEM_PATHS when finding upstream BoostConfig Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5408
| | * | FindBoost: Honor BOOST_ROOT when finding upstream BoostConfigBrad King2020-10-221-0/+6
| | | | | | | | | | | | | | | | Fixes: #21200
| | * | FindBoost: Honor Boost_NO_SYSTEM_PATHS when finding upstream BoostConfigBrad King2020-10-221-1/+6
| | | | | | | | | | | | | | | | Issue: #21200
| * | | Help: Cleanup typos and grammar for the 3.19 releaseCraig Scott2020-10-243-12/+9
| |/ /
| * | Merge topic 'FindPython-support-version-3.10' into release-3.19Brad King2020-10-191-1/+1
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | 23cd98a66a FindPython: Add support of version 3.10 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5383
| | * | FindPython: Add support of version 3.10Marc Chevrier2020-10-161-1/+1
| | |/
| * | Merge topic 'CheckSource-Fortran' into release-3.19Brad King2020-10-164-9/+19
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | c4c636cef5 Tests: Add cases for CheckSource{Compiles,Runs} bad arguments 1e519df025 CheckSource{Runs,Compiles}: Fix default Fortran source extension Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5378
| | * | CheckSource{Runs,Compiles}: Fix default Fortran source extensionMichael Hirsch2020-10-154-9/+19
| | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit 357e2ef429 (CheckSoureRuns: Add a unified way to check if a source runs, 2020-09-14, v3.19.0-rc1~118^2), the default Fortran source file extension was accidentally changed from `.F90` to `.F`. Fix that. In commit 10ae907de0 (CheckSoureCompiles: Add a unified way to check if a source compiles, 2020-09-14, v3.19.0-rc1~118^2~1), the default Fortran source extension was correctly preserved as `.F`, but `.F90` is a better default both for consistency and modern usage. Use that for direct calls to the `check_source_compiles` macro. Update our original `check_fortran_source_compiles` implementation to use `.F` by default as it did before. Fixes: #21307
| * | IAR: Use .o object file extension with IAR-Ilink toolchainsFelipe Torrezan2020-10-151-0/+1
| |/ | | | | | | | | The compiler default extension for its objects is `.o`. Prefer that over `.obj`.
| * Android: show supported API level in error messageHaibo Huang2020-10-131-1/+2
| |
| * Merge topic 'android-verify-abi-in-ndk' into release-3.19Brad King2020-10-131-0/+6
| |\ | | | | | | | | | | | | | | | | | | 5c2f9e3eeb Android: Fatal if ABI is not supported by NDK Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !5351
| | * Android: Fatal if ABI is not supported by NDKHaibo Huang2020-10-091-0/+6
| | |
| * | FindPython: Ensure Apple Xcode python 3 is usableMarc Chevrier2020-10-124-0/+37
| | | | | | | | | | | | | | | | | | | | | The python 3 distributed as part of Xcode requires the specification of a 'rpath' pointing at frameowrks root for a correct execution. Fixes: #21293
generated by cgit v0.12 at 2025-01-22 12:23:55 (GMT)