Brad King authored 3 years ago and Kitware Robot committed 3 years ago

6d4c51c2 IRSL: Add Intel oneAPI redist location on Windows

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6199

Fixes: #22283

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

c44dfdfd FindBoost: Add check for json component header in Boost 1.75+

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Ben Boeckel <ben.boeckel@kitware.com>
Merge-request: !6193

John Drouhard authored 3 years ago and Brad King committed 3 years ago

In commit 82930647 (FindBoost: Add support for Boost 1.75, 2021-02-03,
v3.19.5~9^2) the dependencies of the json component were added, but the
header listing was left out.

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

9d7ebb47 ci: use consistent sccache builds

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6156

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

886e2706 Clang/MSVC: C++20 final flag, C++23 support
3aaf1d91 MSVC: C++20 final flag, C++23 support

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Alex <leha-bot@yandex.ru>
Acked-by: Michael Hirsch <michael@scivision.dev>
Merge-request: !6174

Added in LLVM commit a8f75d497daa2684a03909d7c31d5bce11b427e1, will be released
in 13.0.

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

316cbbe8 Makefiles: Fix CMAKE_EXPORT_COMPILE_COMMANDS crash with custom compile rule

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6173

Microsoft intends to ship the final C++20 flag in VS 16.11 albeit with a few
parts missing due planned ABI breaking changes.
The current 16.11 Preview 1 toolchain version is 19.29.30129.3, so let's
restrict based on that.

Extend the fix from commit 67e2130c (Makefiles: Fix
CMAKE_EXPORT_COMPILE_COMMANDS crash with custom compile rule,
2020-11-20, v3.19.1~8^2) to work for the `<FLAGS>` placeholder too.
Also fix the test case to actually enable `EXPORT_COMPILE_COMMANDS`
on the test target.

Fixes: #22261

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

59d9fa71 gitlab-ci: Update Windows builds to MSVC 19.29-16.10 toolset

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6172

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

9054cd05 VS: Add flag table entries for '/external:W*' flags in VS 16.10

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6171

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

a60141fe VS: Add special case for '-T version=14.29.16.10' under VS 16.10

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6169

Fixes: #22255

Extend the table of special cases from commit 58a50a3a (VS: Fix '-T
version=14.28' under VS 16.9, 2021-03-11, v3.19.7~1^2~1).  Add a special
case for the name VS 16.11 will use for VS 16.10's default toolset, so
that it can be used with VS 16.10 too.

Using '-T version=14.29.16.10' actually works under VS 16.10 without
this change, but only because there is only one 14.29 toolset so the
two-component prefix happens to match the right one.  Make it explicit.

Issue: #21922

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

38f2562d CMP0082: Check EXCLUDE_FROM_ALL property at generate time

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6158

Fixes: #22234

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

8a9753e4 ExternalProject: Only add git config setting with git 1.7.7 or later

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6145

1cb65e68 (ExternalProject: Prevent the noisy detached head
messages on checkout, 2021-01-17) unconditionally added the advice.detachedHead
git config setting, but it requires git 1.7.7 or later. Since it isn't fatal to not
have it, just noisier, only add it when it is supported.

Fixes: #22206

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

364f6af1 NVHPC: Support Ninja dependency scanning
521cfc38 NVHPC: Support explicit language flags

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6136

Fixes: #22168

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

bb9c69ed Utilities/Sphinx: Update man page config for Sphinx 4

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6126

Sphinx 4 by default generates `man/#/foo.#`, but older versions generate
`man/foo.#` as our install rules expect.  Update our Sphinx config file
to tell Sphinx 4 to use the old layout.

Fixes: #22192

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

f78b167a cmCommandLineArgument: Provide more information syntax error messages
5aa0dec6 cmake: `--build` and `--install` error out when encountering bad flags
928cdb17 cmCommandLineArgument: Correctly record parsing failures

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6119

Fixes #22186

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

3a715344 Ninja: Restore support for Fortran in a symlinked build tree

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6120

Since commit f3eed2c4 (cmGlobalNinjaGenerator: use P1689 dependency
file format for Fortran, 2019-03-12, v3.20.0-rc1~454^2), Fortran stopped
working in a build tree whose path contains a symlink.  The reason is
that the P1689r3 format's `work-directory` field gets populated with the
realpath (via `getcwd`) of the build tree instead of the logical path to
the build tree used for generating relative paths in `build.ninja`.
This causes the `Fortran.dd` file to get absolute (real)paths to `.o`
files, and Ninja does not match them with the relative `.o` file paths
in `build.ninja`.

Fix this by dropping use of the `work-directory` field.  This restores
our prior approach of generating paths in the dyndep file using the same
forms of paths received from the buildsystem generator.  The P1689r3
paper's format may need to be revised to account for this.

Fixes: #21683

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

9fbbebe3 GNU: C++23 support
c9a1e06a GNU: Final C++20 flags
05f8c817 GNU: C++17 default version

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6108

Raul Tambre authored 3 years ago and Brad King committed 3 years ago

Added in GCC commit 78739c2df788ee5c868d998a6333d453317d8711, released in 11.1.
No lettered variant beforehand this time around.

Implements #22139.

Raul Tambre authored 3 years ago and Brad King committed 3 years ago

Added in GCC commit fb26050409473f5be54465beca114b7e48de43aa, released in 11.1.

Raul Tambre authored 3 years ago and Brad King committed 3 years ago

Changed in GCC commit 0801f419440c14f6772b28f763ad7d40f7f7a580, released in 11.1.

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

79be37b9 FindBoost: Add support for Boost 1.76

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6100

Brad King authored 3 years ago and Kitware Robot committed 3 years ago

5e941a54 ExternalProject: Ensure git fetch if updating to hash we don't have yet

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Ben Boeckel <ben.boeckel@kitware.com>
Merge-request: !6109

In ac6a4d48 (ExternalProject: Improve robustness of update step,
2020-10-17), the method used to check whether we already have a
commit or not was changed from using git rev-list to git rev-parse.
The new logic assumed rev-parse would output nothing if given a commit
hash it didn't know about, but it simply prints the hash again without
raising an error in this scenario. Amend that logic by adding ^{commit} to
the ref to ensure we do get an error if that ref is not currently known.

Fixes: #22166