summaryrefslogtreecommitdiffstats
path: root/Modules
Commit message (Collapse)AuthorAgeFilesLines
* IAR: decouple linker location from toolkit's bin dirFelipe Torrezan2025-01-211-6/+6
| | | | | | | | | | | | | | | The implementation in commit 564d527c04 (IAR: Improve error message for missing license, 2024-08-12, v3.31.0-rc1~234^2) failed for corner cases in which symlinks were used from a location different from the one in which the toolkit is shipped with (`<target>/bin`). In this new implementation, the `<target>` architecture is taken solely from the compiler NAME itself for all the supported languages and forwarded to its respective BinUtils executable names (e.g., `icc<target>`, `iasm<target>`, `a<target>`). This decouples the location from the subdirectory in which they should be found. Fixes: #26610
* Merge topic 'FindMatlab-doc' into release-3.31Brad King2025-01-171-5/+7
|\ | | | | | | | | | | | | 6e21dcc0ee FindMatlab: Fix multi-signature function documentation anchors Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !10186
| * FindMatlab: Fix multi-signature function documentation anchorsBrad King2025-01-161-5/+7
| | | | | | | | | | | | | | Fix use of the `signature::` directive by commit ae558b9ad0 (FindMatlab: Support REGISTRY_VIEW, 2024-02-08, v3.30.0-rc1~528^2). The directive was created for use inside `Help/command/*.rst` documents. Using it in module documentation requires explicit anchors.
* | Clang/CUDA: Fix language-wide flags when linking .so with compiler driverBrad King2025-01-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | In commit cfa888a6e2 (Clang/CUDA: Add language-wide flags when linking with compiler driver, 2024-10-07, v3.31.0-rc1~12^2) we added the wrong placeholder to `CMAKE_CUDA_CREATE_SHARED_LIBRARY` to represent the language-wide flags. The `<FLAGS>` placeholder is for executables. The `<LANGUAGE_COMPILE_FLAGS>` placeholder is for shared libraries. The distinction is for historical reasons. Fixes: #26563
* | Merge topic 'lfortran-generate-object-code' into release-3.31Brad King2025-01-103-2/+6
|\ \ | | | | | | | | | | | | | | | | | | daf6cc89ee LFortran: Remove hard-coded --generate-object-code flag Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !10159
| * | LFortran: Remove hard-coded --generate-object-code flagSaurabh Kumar2025-01-093-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This was added in commit 98d0f918ba (LFortran: Add support for this compiler, 2024-01-25, v3.31.0-rc1~303^2~2) because it is needed for cases covered by CMake's Fortran tests. However, it does not work with Fortran modules and breaks lfortran's own `examples/project1`. Move the flag to the test cases that need it, just as the original commit did with `--implicit-interface`. Fixes: #26597 Co-authored-by: Brad King <brad.king@kitware.com>
* | | Merge topic 'FindBoost-1.87' into release-3.31Brad King2025-01-081-3/+17
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | f485f94d1a FindBoost: Add support for Boost 1.87 Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !10147
| * | | FindBoost: Add support for Boost 1.87Brad King2025-01-071-3/+17
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update the list of known versions. Run the command cmake -DBOOST_DIR=/path/to/boost_1_87_0 \ -P Utilities/Scripts/BoostScanDeps.cmake to extract dependencies from the 1.87.0 source tree. Dependencies differ from 1.86: * Boost.Log no longer depends on Boost.Chrono Fixes: #26562
* | | Help: FindPython: fix typoMarc Chevrier2024-12-213-3/+3
|/ /
* | VS: Restore support for mixing C++23 and C in one target with clang-clBrad King2024-12-091-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | Since commit 474eafe28c (clang-cl: Add support for C++23, 2024-09-13, v3.31.0-rc1~97^2) we use a Clang-specific flag to enable C++23 since `clang-cl` has no `-std:c++23` flag, and `-std:c++latest` may enable an even newer version of C++. However, in `.vcxproj` files there is no way to express a target-wide `-clang:-std=c++23` flag for only C++ sources when the target also has C sources. Add a special case to map back to `-std:c++latest` for targets with C++23 and C together. Fixes: #26508
* | Merge topic 'FindPython-SABIModule-handling' into release-3.31Brad King2024-12-031-3/+4
|\ \ | | | | | | | | | | | | | | | | | | | | | ff65c5fca0 FindPython: Ensure SABIModule is found in all cases Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !10058
| * | FindPython: Ensure SABIModule is found in all casesMarc Chevrier2024-12-021-3/+4
| | | | | | | | | | | | Fixes: #26493
* | | FindRuby: Add support for 3.4cfis2024-12-021-15/+10
|/ /
* | Merge topic 'linker-depfile-flag' into release-3.31Brad King2024-11-291-1/+1
|\ \ | | | | | | | | | | | | | | | | | | f4e74af1ea GNU linker: Use single-argument form of --dependency-file flag Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !10049
| * | GNU linker: Use single-argument form of --dependency-file flagBrad King2024-11-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The GNU `ld(1)` manual documents the `--dependency-file=depfile` single-argument form of the flag. Prefer it over the multi-argument `--dependency-file depfile` form so that only one argument needs to be passed through the compiler driver by `-Wl,` or equivalent. This may improve diagnostics in cases where it is unsupported, making them easier to diagnose. Issue: #26483
* | | Intel/Classic: deactivate linker dependency file supportMarc Chevrier2024-11-281-0/+3
|/ / | | | | | | | | | | | | The Intel Classic compilers' IPO plugins do not support the `-Wl,--dependency-file,...` linker flag. Fixes: #26483
* | LLD linker: avoid regression on archive libraries deduplicationMarc Chevrier2024-11-1834-0/+49
| | | | | | | | | | | | | | Due to a bug on LLD linker for ELF binaries, deduplication should occur only if CMP0156 and CMP0179 are NEW. Fixes: #26447
* | Merge topic 'musl-linux-any' into release-3.31Brad King2024-11-131-1/+1
|\ \ | | | | | | | | | | | | | | | | | | d8559ec92e Linux: Recognize multiarch directories for musl-linux-any Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !9991
| * | Linux: Recognize multiarch directories for musl-linux-anyTimo Röhling2024-11-121-1/+1
| | | | | | | | | | | | | | | | | | | | | When bootstrapping Debian for musl-linux-any, the multiarch directories are not found due to an overly-specific regular expression. See https://bugs.debian.org/1085507 for the original bug report.
* | | Merge topic 'image-magick-7' into release-3.31Brad King2024-11-131-1/+3
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | f6c6032e22 FindImageMagick: Fix ARCH_INCLUDE_DIR detection for version 7 and newer Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !9990
| * | | FindImageMagick: Fix ARCH_INCLUDE_DIR detection for version 7 and newerTimo Röhling2024-11-121-1/+3
| |/ / | | | | | | | | | | | | | | | The `magick-baseconfig.h` header has been moved to a different subdirectory. See https://bugs.debian.org/1087233 for the original bug report in Debian.
* | | Merge topic 'WHOLE_ARCHIVE-various-systems' into release-3.31Brad King2024-11-1350-9/+246
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | d2997ab601 Linker configuration: Add missing platforms Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !9992
| * | | Linker configuration: Add missing platformsMarc Chevrier2024-11-1250-9/+246
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The following platforms were missing: * Android * WindowsCE, WindowsPhone, WindowsStore and WindowsKernelModeDriver And enhance various Apple platforms support (iOS, tvOS, etc...) Fixes: #26439
* | | | Merge topic 'gtest-discover-flush-duplicates' into release-3.31Brad King2024-11-131-39/+31
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | 007d7ea648 GoogleTest: Avoid extra call to set DISABLED test property in discovery 9a24c1e802 GoogleTest: Clear script content buffer on flush and flush less often Acked-by: Kitware Robot <kwrobot@kitware.com> Tested-by: buildbot <buildbot@kitware.com> Merge-request: !9982
| * | | GoogleTest: Avoid extra call to set DISABLED test property in discoveryCraig Scott2024-11-121-4/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For very long test names, this can noticeably reduce the size of the generated file contents when tests are disabled. This change reduces how far beyond the flush threshold the content can grow before being flushed. Issue: #26431
| * | | GoogleTest: Clear script content buffer on flush and flush less oftenCraig Scott2024-11-121-35/+28
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There's no need to check if flushing is needed after every command is added to the variable holding the script content. It is enough to only check once per test name. This simplifies the flushing logic, removing the need for a separate flush_script() command. Previously, we were not clearing the flushed script contents in all cases, but this is now rigorously enforced at the one location where flushing is performed. Also simplify the flushing of the list of test names, since that too doesn't need a separate command. It is simpler and safer to handle that directly inline where the one call to flush_tests_buffer() was previously being made. Fixes: #26431
* | | Merge topic 'FindSQLite3-pkg-config' into release-3.31Brad King2024-11-121-1/+3
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2d228201fc Help: Guard calls to pkg_check_modules in cmake-developer(7) example 674a987898 FindSQLite3: Guard calls to pkg_check_modules Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !9983
| * | | FindSQLite3: Guard calls to pkg_check_modulesPeter Kokot2024-11-111-1/+3
| |/ / | | | | | | | | | | | | This was missed in commit 25b947589a (Modules: Guard calls to pkg_check_modules, 2024-08-07, v3.31.0-rc1~236^2).
* | | Merge topic 'FindBoost-1.86' into release-3.31Brad King2024-11-121-2/+2
|\ \ \ | |/ / |/| / | |/ | | | | | | f941fb6c0b FindBoost: Add support for Boost 1.86 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !9988
| * FindBoost: Add support for Boost 1.86Brad King2024-11-111-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update the list of known versions. Run the command cmake -DBOOST_DIR=/path/to/boost_1_86_0 \ -P Utilities/Scripts/BoostScanDeps.cmake to extract dependencies from the 1.86.0 source tree. They are the same as 1.85's dependencies, so just update the version check for warning about newer versions. Fixes: #26433
* | Merge topic 'FindCUDAToolkit-remove-debug-message' into release-3.31Brad King2024-10-281-1/+0
|\ \ | | | | | | | | | | | | | | | | | | | | | fb0b3d1585 FindCUDAToolkit: Remove debug message Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Robert Maynard <robertjmaynard@gmail.com> Merge-request: !9946
| * | FindCUDAToolkit: Remove debug messageSeth R Johnson2024-10-251-1/+0
| | | | | | | | | | | | | | | | | | This was left accidentally by commit 587c0443cc (FindCUDAToolkit: Support CUDA version extraction from version.json, 2023-05-02, v3.26.4~3^2).
* | | codespell: Fix typosBrad King2024-10-252-3/+3
|/ /
* | Merge topic 'windows-kernel-mode-driver' into release-3.31Brad King2024-10-251-9/+4
|\ \ | | | | | | | | | | | | | | | | | | | | | 54bbd00448 WindowsKernelModeDriver: Switch to appending to variables Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !9941
| * | WindowsKernelModeDriver: Switch to appending to variablesJoseph Snyder2024-10-241-9/+4
| | | | | | | | | | | | | | | | | | | | | | | | When using the WindowsKernelModeDriver, do not add the new paths if the variable was not previously defined. Instead, append them to the existing value. Add a new GUID for the Experimental mode gate
* | | Merge topic 'lfortran-link-info' into release-3.31Brad King2024-10-252-8/+9
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 34067963cc LFortran: Improve detection of implicit link information for lfortran 0.40+ Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !9939
| * | | LFortran: Improve detection of implicit link information for lfortran 0.40+Brad King2024-10-242-8/+9
| |/ / | | | | | | | | | | | | | | | | | | These versions of LFortran support passing `-v -Wl,-v` to the underlying compiler so we can extract the full implicit link information. Issue: #26145
* | | Linker configuration: enhance usabilityMarc Chevrier2024-10-2418-42/+38
|/ / | | | | | | | | | | | | | | | | | | The linker configuration file is now optional: It is loaded only if variable CMAKE_<LANG>_USE_LINKER_CONFIGURATION is set to TRUE. The file CMakeAddNewLanguage.txt is updated to take into account the linker configuration. Fixes: #26393
* | Merge topic 'python3.14' into release-3.31Brad King2024-10-183-3/+3
|\ \ | |/ | | | | | | | | | | be958c8f35 FindPython: Add support for Python 3.14 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !9915
| * FindPython: Add support for Python 3.14Miro Hrončok2024-10-183-3/+3
| |
| * Merge topic 'cpack-nuget-native' into release-3.30Brad King2024-09-201-0/+3
| |\ | | | | | | | | | | | | | | | | | | c358872976 CPack/NuGet: Add native0.0 to build dependencies in groups Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !9829
* | | Xcode: Use ad-hoc signing during compiler id for iOS Mac CatalystBrad King2024-10-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | In commit 2785364b7b (iOS: Add support for Mac Catalyst, 2024-07-02, v3.31.0-rc1~371^2) we forgot to update the conditions to use ad-hoc signing from commit 89e1113e0c (Xcode: Use ad-hoc signing during compiler id on macOS, 2022-06-10, v3.22.6~4^2~2). Fixes: #26376
* | | FindCUDAToolkit: nvrtc shouldn't hard depend on nvJitLinkRobert Maynard2024-10-141-2/+2
| | | | | | | | | | | | | | | The dependency on nvJitLink was due to misunderstanding how runtime compiled code that uses LTO is used. It doesn't require nvrtc to have a dependency on nvJitLink, just the caller.
* | | CUDAToolkit: nvrtc shouldn't hard depend on nvrtc-builtinsRobert Maynard2024-10-091-1/+1
| | | | | | | | | | | | | | | | | | Depending on nvrtc-builtins breaks CUDA enhanced compatibility across minor versions. The static version of nvrtc continues to need the dependency due to undefined symbols
* | | Merge topic 'FindProtobuf-protoc-missing'Brad King2024-10-091-0/+6
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 4a1177246d FindProtobuf: Fail protobuf_generate early if protoc is missing Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !9880
| * | | FindProtobuf: Fail protobuf_generate early if protoc is missingJiaRui Liu2024-10-081-0/+6
| | | |
* | | | FindOpenMP: Add support for CUDA when compiling with ClangBrad King2024-10-071-5/+3
| | | |
* | | | Clang/CUDA: Add language-wide flags when linking with compiler driverBrad King2024-10-071-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | We do this for other compiler/language combinations, but these flags were left out by commit 5df21adf46 (CUDA: Add support for Clang compiler, 2020-03-07, v3.18.0-rc1~145^2~1).
* | | | Merge topic 'GoogleTest-DISCOVERY_EXTRA_ARGS'Brad King2024-10-072-2/+26
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2dcba446e2 GoogleTest: Add DISCOVERY_EXTRA_ARGS to gtest_discover_tests() f55f9fd5c1 Help: Mention TEST_LIST with gtest_discover_tests() can omit tests Acked-by: Kitware Robot <kwrobot@kitware.com> Tested-by: buildbot <buildbot@kitware.com> Merge-request: !9856
| * | | | GoogleTest: Add DISCOVERY_EXTRA_ARGS to gtest_discover_tests()Cedric Martineau2024-10-042-1/+19
| | | | | | | | | | | | | | | | | | | | | | | | | Fixes: #26261 Co-authored-by: Craig Scott <craig.scott@crascit.com>
generated by cgit v0.12 at 2026-02-12 14:28:42 (GMT)