| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
d870a47e23 Tests/FortranModules: add a test for iface Fortran sources
e3d511fb9c Tests/FortranModules: also test INTERFACE targets with Fortran sources
978b68d3bb add_custom_target: Fix regression with Fortran sources
619aca80ae Tests/FortranModules: add a test case for #25223
45513c1a69 Tests/FortranModules: move issue 25112 fix from FortranOnly
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8814
|
| |
| |
| |
| |
| | |
This tests that a library that doesn't compile Fortran sources but
provides one via `INTERFACE` sources works as intended.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since commit 74b1d6caf3 (cmComputeLinkInformation: compute link info for
module-using targets, 2023-09-05, v3.27.5~7^2) we accidentally try to
compute link information for custom targets if they have Fortran
sources. For module dependencies, we only need to consider target types
that can compile.
Fixes: #25252
|
| | |
|
|/
|
|
| |
It involves modules, so it belongs in the `FortranModules` test set.
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
458e3974a8 cxxmodules: detect and message about non-compiled sources
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8773
|
| |
| |
| |
| |
| |
| |
| |
| | |
Previously an internal error was raised which ended up causing an
internal exception to be thrown. This is a typo situation that should
fall into an explicit error.
Fixes: #25207
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
42adf3cba8 Autogen: Evaluate INTERFACE_AUTOMOC_MACRO_NAMES efficiently
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8799
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
In commit c5c3aff1f5 (Autogen: Add INTERFACE_AUTOMOC_MACRO_NAMES target
property, 2023-04-03, v3.27.0-rc1~197^2) we forgot to mark the property
as a usage requirement. This is needed for efficient evaluation over
the target dependency closure.
Fixes: #25238
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
6ebff6ebf8 VS: Avoid unnecessary CUDA device linking for OBJECT libraries
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8794
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Without `CudaLink` fields, MSBuild tries to perform a device link step
for object libraries with CUDA_SEPARABLE_COMPILATION on them even when
not needed. This commonly was encountered when generating PTX or
OPTIX-IR output.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
897a149067 FindBoost: Add support for Boost 1.83
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8793
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Update the list of known versions.
Run the command
cmake -DBOOST_DIR=/path/to/boost_1_83_0 \
-P Utilities/Scripts/BoostScanDeps.cmake
to extract dependencies from the 1.83.0 source tree.
Dependencies differ from 1.82, as mentioned in the 1.83 release notes:
* Boost.Timer no longer depends on Boost.Chrono
Fixes: #25243
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
84a097f038 FortranCInterface: forward `CMAKE_OSX_DEPLOYMENT_TARGET`
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8790
|
|/ / /
| | |
| | |
| | |
| | | |
GCC needs to be taught about every macOS release it seems, so older
builds may not support usage on newer releases by default.
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
26ce8dc290 ctest: Restore support for http redirects during Submit step
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8782
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
After CDash PR 1519 introduced HTTP status codes greater than 200 for
various error cases, CMake commit b7c871f745 (ctest: Update ctest_submit
for CDash behavior change, 2023-07-24, v3.27.1~3^2) modified CTest's
submit handler to check the status returned by CDash and throw an error
when this status is not equal to 200.
That change had the unintended side effect of causing CTest submissions
to fail when uploading results to a URL that returns a redirect status
code (3xx). Fix this by configuring cURL to follow the redirect. The
status cURL reports to CTest is now 200 instead of 3xx when CDash is
located behind a redirect.
Fixes: #25159
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
74b1d6caf3 cmComputeLinkInformation: compute link info for module-using targets
6251edaed1 cmGeneratorTarget: support config-independent Fortran source queries
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8772
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Targets which contain C++ module or Fortran sources need to participate
in link information unconditionally regardless of whether they actually
have link artifacts or not.
Fixes: #25223
|
| |/
| |
| |
| |
| | |
Some locations care about "any config with Fortran", so make a query for
such (they may not know any configuration names themselves).
|
|\ \
| |/
|/|
| |
| |
| |
| | |
91dc94c4ac Help: MSVC_DEBUG_INFORMATION_FORMAT is initialized from associated variable
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8770
|
|/
|
|
|
|
|
|
|
|
|
| |
The `CMAKE_MSVC_DEBUG_INFORMATION_FORMAT` variable docs mention that it
initializes the `MSVC_DEBUG_INFORMATION_FORMAT` target property, but the
property's docs was missing any mention of the variable.
Follow the pattern from commit c1b07ca9da (Help: MSVC_RUNTIME_LIBRARY is
initialized from associated variable, 2022-08-13, v3.25.0-rc1~317^2).
Fixes: #25216
|
|\
| |
| |
| |
| |
| |
| | |
fa3c4b6dbf Source: Link libatomic when needed on any Linux architecture
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8756
|
|/
|
|
|
|
|
|
| |
Extend commit 78bbd58545 (Source: Link libatomic when needed on Linux
32-bit ARM, 2023-07-27, v3.27.2~10^2) to check for libatomic on more
architectures.
Fixes: #25204
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
9034394950 FindZLIB: Fix extraction of two-component version number 1.3
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8753
|
|/
|
|
| |
Fixes: #25200
|
|\
| |
| |
| |
| |
| |
| |
| | |
741755f637 Help: Document cmake_minimum_required deprecation of old versions
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: scivision <michael@scivision.dev>
Merge-request: !8742
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Document the deprecation warnings added by commit 5845c218d7 (Deprecate
compatibility with CMake versions older than 2.8.12, 2020-06-12,
v3.19.0-rc1~629^2) and commit 3a4791548d (Deprecate compatibility with
CMake versions older than 3.5, 2023-02-09, v3.27.0-rc1~508^2).
Fixes: #25196
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
1140087ade LLVMFlang-Fortran: Add flags for build types
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8741
|
| |/
| |
| |
| | |
Fixes: #25193
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
e4fe26201f VS: Remove duplicate import in compiler id vcxproj
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8740
|
| |/
| |
| |
| |
| |
| |
| | |
Since commit d3c4c6d630 (VS: Import default C++ props file before
toolset-specific props file, 2023-03-01, v3.27.0-rc1~361^2) we import
`Microsoft.Cpp.Default.props` twice. Remove the extra import line, and
re-order imports as intended by the original change.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
90df1e5da4 Merge branch 'upstream-cppdap' into update-cppdap
5d568df6b1 cppdap 2023-08-17 (cc2f2058)
01d2e5ed3a cppdap: Update script to get version as of 2023-08-17
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8739
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | | |
# By cppdap Upstream
* upstream-cppdap:
cppdap 2023-08-17 (cc2f2058)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Code extracted from:
https://github.com/google/cppdap.git
at commit cc2f2058846bb29e18fdadf455d5f5af71b2554f (cc2f2058846bb29e18fdadf455d5f5af71b2554f).
|
| | |/
| |/| |
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
45ed175f08 list(INSERT): restore old behavior
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8732
|
|/ /
| |
| |
| | |
Fixes: #25191
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
30b1080c69 Utilities/Release: Remove unused documentation build settings
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8730
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since commit 37e015d4a6 (Utilities/Sphinx: Refactor Sphinx reference
recording, 2023-03-08, v3.27.0-rc1~342^2~1) our documentation requires
Python 3.7 or higher. This is not available in the base images we use
to build Linux release binaries. These days our release packaging CI
pipeline builds the documentation in a separate job anyway.
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
1a5cb0c1c1 testDebuggerNamedPipe: fix for cppdap with nlohmann_json
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8725
|
| | |
| | |
| | |
| | |
| | | |
Fixes: #25190
Signed-off-by: Đoàn Trần Công Danh <congdanhqx@gmail.com>
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
7f7c443667 Unity: use C-style comments to work both with C and C++
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8718
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Update the comment added by commit 485256f2d0 (Unity: Suppress
clang-tidy 'bugprone-suspicious-include' warning, 2023-04-27,
v3.27.0-rc1~149^2) to work for C.
Fixes: #25184
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
5a41d926dd GHS: Escape custom command comments
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8714
|