| 2a5e5b2 | Brad King | 30 October 2019, 13:44:41 UTC | CMake 3.15.5 | 30 October 2019, 13:44:41 UTC |
| 0817307 | Brad King | 21 October 2019, 14:26:48 UTC | Merge branch 'doc-genex-tweak' into release-3.15 Merge-request: !3939 | 21 October 2019, 14:26:48 UTC |
| c684db4 | Alan W. Irwin | 21 October 2019, 14:21:16 UTC | Help: Fix COMPILE_LANG_AND_ID genex example Fix the `COMPILE_LANGUAGE/CXX_COMPILER_ID` variant of the example to have the same meaning as the `COMPILE_LANG_AND_ID` variant. The inconsistency was introduced by commit 808b818063 (Genex: CompileLang and CompileLangAndId now match against a list of ids, 2019-05-30, v3.15.0-rc1~11^2~1). Fixes: #19862 | 21 October 2019, 14:25:41 UTC |
| 83dbef1 | Brad King | 11 October 2019, 16:08:27 UTC | Merge branch 'InstallRequiredSystemLibraries-redist' into release-3.15 Merge-request: !3909 | 11 October 2019, 16:08:27 UTC |
| ecbf654 | Brad King | 11 October 2019, 16:04:28 UTC | IRSL: Install vcruntime140_1.dll if available VS 2019 now distributes this additional runtime DLL with its `14.2x` toolsets. Fixes: #19829 | 11 October 2019, 16:05:51 UTC |
| 2eecd1c | Brad King | 11 October 2019, 15:57:39 UTC | IRSL: Prefer MSVC runtime libraries from newest toolset first | 11 October 2019, 15:57:39 UTC |
| 881bca2 | Brad King | 11 October 2019, 15:18:41 UTC | Merge branch 'vs-v142-csharp-flags' into release-3.15 Merge-request: !3908 | 11 October 2019, 15:18:41 UTC |
| bbf216f | Brad King | 11 October 2019, 14:42:47 UTC | VS: Add toolset v142 CSharp flag table While the flag tables for C and C++ were generated from MSBuild `.xml` files, the CSharp flag tables were written by hand. Copy the `v141` flag table to use for the `v142` toolset. Remove the special case added by commit 626c51f47b (VS: Update for Visual Studio 2019 Preview 2, 2019-01-24, v3.14.0-rc1~74^2) that mapped the v142 flag table lookup to v141 since we now have the real v142 table. Fixes: #19828 | 11 October 2019, 15:11:20 UTC |
| dec3e93 | Brad King | 07 October 2019, 21:49:17 UTC | Merge branch 'backport-vs-16.4-global-targets' into release-3.15 Merge-request: !3896 | 07 October 2019, 21:51:51 UTC |
| ac1a1bf | Brad King | 07 October 2019, 21:35:53 UTC | VS: Tell VS 16.4 not to verify CMake-provided custom command outputs Extend the fix from commit 0578239d3a (VS: Tell VS 16.4 not to verify SYMBOLIC custom command outputs, 2019-09-23, v3.15.4~2^2) to apply to outputs in CMake-provided targets like `install`. Simply mark these outputs as `SYMBOLIC` too since they are not actually generated. Fixes: #19737 | 07 October 2019, 21:44:32 UTC |
| b21e4e4 | Brad King | 02 October 2019, 12:25:27 UTC | Merge branch 'backport-xcode-scheme-custom-target' into release-3.15 Merge-request: !3878 | 02 October 2019, 12:25:27 UTC |
| ac99344 | Brad King | 02 October 2019, 12:15:05 UTC | Xcode: Restore CMAKE_XCODE_GENERATE_SCHEME for custom targets The target property introduced by commit 413b71485a (Xcode: Create Xcode schemes per target, 2019-03-11, v3.15.0-rc1~347^2) was accidentally not initialized by `CMAKE_XCODE_GENERATE_SCHEME` for custom targets. Fix it and update the test. Fixes: #19759 | 02 October 2019, 12:17:32 UTC |
| f695b6b | Brad King | 01 October 2019, 15:41:32 UTC | Merge branch 'vs-v142-version' into release-3.15 Merge-request: !3874 | 01 October 2019, 15:41:32 UTC |
| 5117389 | Brad King | 01 October 2019, 15:23:12 UTC | VS: Fix support for v142 toolset minor versions When using `-T v142,version=14.22` the `.props` file location is different starting with version `14.20` than it was in `14.16` and below. Adapt the path based on the version. Fixes: #19779 | 01 October 2019, 15:39:38 UTC |
| 6fb747a | Brad King | 30 September 2019, 19:30:00 UTC | CMake 3.15.4 | 30 September 2019, 19:30:00 UTC |
| e7637a3 | Brad King | 30 September 2019, 14:29:11 UTC | Merge branch 'backport-3.15-fix-EXCLUDE_FROM_ALL-subdir-all' into release-3.15 Merge-request: !3863 | 30 September 2019, 14:29:11 UTC |
| 013d7dd | Brad King | 24 September 2019, 18:31:23 UTC | Help: Mention 3.14.7 EXCLUDE_FROM_ALL fix in 3.15.4 release note | 30 September 2019, 13:20:55 UTC |
| 61103c0 | Brad King | 30 September 2019, 13:20:40 UTC | Merge branch 'backport-3.14-fix-EXCLUDE_FROM_ALL-subdir-all' | 30 September 2019, 13:20:40 UTC |
| 1fe4501 | Brad King | 24 September 2019, 18:31:00 UTC | Help: Add release note for EXCLUDE_FROM_ALL fix in 3.15.4 | 30 September 2019, 13:20:35 UTC |
| 05d7ca1 | Brad King | 30 September 2019, 13:19:21 UTC | Merge branch 'backport-3.14-fix-EXCLUDE_FROM_ALL-subdir-all' | 30 September 2019, 13:19:21 UTC |
| 62d45d9 | Brad King | 24 September 2019, 18:24:55 UTC | Help: Add release note for EXCLUDE_FROM_ALL fix in 3.14.7 | 30 September 2019, 13:18:20 UTC |
| b3b1c7b | Brad King | 24 September 2019, 15:50:18 UTC | Restore "all" target in subdirectories marked EXCLUDE_FROM_ALL The "all" target in each directory is supposed to have targets from that directory even if the directory itself is marked `EXCLUDE_FROM_ALL` in its parent. This was broken by commit dc6888573d (Pass EXCLUDE_FROM_ALL from directory to targets, 2019-01-15, v3.14.0-rc1~83^2) which made the participation of a target in "all" independent of context. Revert much of the logic change from that commit to restore the old behavior. Then re-implement the behavior intended by the commit to keep its test working. Extend the test to cover the old behavior too. Fixes: #19753 | 30 September 2019, 13:18:20 UTC |
| 156b564 | Brad King | 27 September 2019, 17:06:56 UTC | Makefiles: Revert "Make build root targets ... recursive" Revert the main logic change from commit 827da1119e (Makefiles: Make build root targets "all", "clean" and "preinstall" recursive, 2019-05-17, v3.15.0-rc1~96^2~2) for the "all" and "preinstall" targets. The commit cleaned up the Makefile generator to use the same logic for the "all" target in the top-level directory as for subdirectories. It exposed a long-existing bug that caused the "all" target in a subdirectory to include the "all" targets from sub-subdirectories even if they are marked `EXCLUDE_FROM_ALL`. The `Tests/SubDir` test should fail but the problem is currently covered up by another bug introduced by commit dc6888573d (Pass EXCLUDE_FROM_ALL from directory to targets, 2019-01-15, v3.14.0-rc1~83^2) that causes the "all" targets in `EXCLUDE_FROM_ALL` subdirectories to be empty. Revert the top-level "all" and "preinstall" targets to the old approach to prepare to fix the latter bug without exposing the long-existing bug at the top-level. Leave the "clean" target in the new approach because it does not honor `EXCLUDE_FROM_ALL` anyway. Issue: #19753 | 27 September 2019, 18:15:00 UTC |
| cf01d3d | Brad King | 26 September 2019, 18:47:53 UTC | Tests: Clarify target names in RunCMake.add_subdirectory ExcludeFromAll Rename the `baz` target to `subinc` to clarify that its role is to be included even though it is in an otherwise excluded subdirectory. | 26 September 2019, 18:58:26 UTC |
| 21442d7 | Brad King | 24 September 2019, 16:39:33 UTC | Tests: Revise RunCMake.add_subdirectory ExcludeFromAll to avoid globbing Also simplify the clean step. | 26 September 2019, 18:57:40 UTC |
| 0cfbd85 | Brad King | 24 September 2019, 17:07:14 UTC | Tests: Teach RunCMake to support a custom working directory | 24 September 2019, 18:10:34 UTC |
| 5a35a9c | Brad King | 24 September 2019, 14:46:13 UTC | Merge branch 'vs-16.4-custom-commands' into release-3.15 Merge-request: !3860 | 24 September 2019, 14:46:13 UTC |
| 0578239 | Brad King | 23 September 2019, 19:30:15 UTC | VS: Tell VS 16.4 not to verify SYMBOLIC custom command outputs VS 16.4 introduces an additional check on `CustomBuild` rules that warns if the outputs of the command are not created. However, CMake supports marking outputs with the `SYMBOLIC` property to indicate that they will not actually be generated. That property is used by Makefile and Ninja generators but has not been needed by the VS generators before. Teach the VS generator to disable `VerifyInputsAndOutputsExist` in custom build rules that have a symbolic output. Fixes: #19737 | 24 September 2019, 14:41:20 UTC |
| 2f702be | Brad King | 20 September 2019, 14:04:46 UTC | Merge branch 'doc-vs-2019-toolset' into release-3.15 Merge-request: !3841 | 20 September 2019, 14:04:46 UTC |
| 67f3dda | LE GARREC Vincent | 20 September 2019, 09:38:04 UTC | Help: Document VS 2019 toolset in MSVC_TOOLSET_VERSION | 20 September 2019, 13:11:40 UTC |
| 26a0e20 | Brad King | 04 September 2019, 13:50:07 UTC | CMake 3.15.3 | 04 September 2019, 13:50:07 UTC |
| 7a8bd12 | Brad King | 04 September 2019, 13:10:57 UTC | Merge branch 'FindBoost-1.71' into release-3.15 Merge-request: !3780 | 04 September 2019, 13:10:57 UTC |
| 907d3ed | Brad King | 04 September 2019, 12:24:09 UTC | FindBoost: Tolerate future Boost INTERFACE libraries Since commit 0dd6772a89 (FindBoost: Add legacy variables and targets for compatibility, 2019-06-14, v3.15.0-rc2~3^2~1) we query imported targets provided by `BoostConfig.cmake` for their `IMPORTED_LOCATION_<cfg>`. Querying this property is not allowed on INTERFACE libraries, so add a condition to avoid doing so in case Boost adds one in the future. Suggested-by: Alexander Grund <alexander.grund@tu-dresden.de> Issue: #19656, #19402 | 04 September 2019, 13:09:31 UTC |
| 2d357b7 | Brad King | 04 September 2019, 13:08:21 UTC | FindBoost: Clarify role of legacy variables in warning message Revise the wording of the warning added by commit 0dd6772a89 (FindBoost: Add legacy variables and targets for compatibility, 2019-06-14, v3.15.0-rc2~3^2~1) to refer to the old variables as "legacy" rather than "standard". Suggested-by: Alexander Grund <alexander.grund@tu-dresden.de> Issue: #19402 | 04 September 2019, 13:09:31 UTC |
| 3b8fa49 | Brad King | 30 August 2019, 18:54:30 UTC | Merge branch 'FindBoost-1.71' into release-3.15 Merge-request: !3763 | 30 August 2019, 18:54:30 UTC |
| 7828577 | Brad King | 30 August 2019, 18:36:32 UTC | FindBoost: Add support for Boost 1.71 Run `Utilities/Scripts/BoostScanDeps.cmake` with the Boost 1.71.0 sources to compute dependencies. They are the same as Boost 1.70. Fixes: #19658 | 30 August 2019, 18:51:20 UTC |
| cf29fa1 | Brad King | 30 August 2019, 18:03:59 UTC | FindBoost: Unwrap compatibility INTERFACE targets for legacy variables Since commit 0dd6772a89 (FindBoost: Add legacy variables and targets for compatibility, 2019-06-14, v3.15.0-rc2~3^2~1) we extract information from imported targets provided by upstream `BoostConfig.cmake` files. However, upstream Boost 1.71 provides some imported targets only for compatibility. They are just INTERFACE libraries that wrap around the real target named by `INTERFACE_LINK_LIBRARIES`. Unwrap this layer so we can extract the real imported location. Fixes: #19656 | 30 August 2019, 18:51:03 UTC |
| d7df3cd | Brad King | 30 August 2019, 18:47:58 UTC | FindBoost: Remove incorrect 1.70 timer dependency Running `Utilities/Scripts/BoostScanDeps.cmake` with the Boost 1.70.0 sources shows that the `timer` component no longer depends on `system`. This is consistent with upstream Boost Timer commit `43eecbd071`. | 30 August 2019, 18:51:03 UTC |
| 8ff43de | Brad King | 30 August 2019, 18:34:14 UTC | FindBoost: Simplify conditional block for last known version A version newer than we know about will be large enough to enter the block for the last known version so we can put the warning there. | 30 August 2019, 18:51:03 UTC |
| 1ae24ee | Brad King | 30 August 2019, 14:21:29 UTC | Merge branch 'fileapi-CMP0037-OLD' into release-3.15 Merge-request: !3760 | 30 August 2019, 14:21:29 UTC |
| 9da1c33 | Brad King | 30 August 2019, 14:18:28 UTC | fileapi: Fix codemodel v2 target file name for CMP0037 OLD behavior With CMP0037 OLD behavior, executable and library target names may contain a slash. Avoid constructing file names with slashes. Fixes: #19653 | 30 August 2019, 14:20:12 UTC |
| aeeccc3 | Brad King | 28 August 2019, 15:28:59 UTC | Merge branch 'backport-find-no-name' into release-3.15 Merge-request: !3751 | 28 August 2019, 15:28:59 UTC |
| 4c8760c | Brad King | 28 August 2019, 14:58:56 UTC | find_path: Fix crash on empty old-style list of names Fixes: #19651 | 28 August 2019, 15:18:53 UTC |
| 1d95305 | Brad King | 27 August 2019, 14:25:53 UTC | Merge branch 'autogen_fix_use_after_move' into release-3.15 Merge-request: !3745 | 27 August 2019, 14:25:53 UTC |
| e32f700 | Sebastian Holtermann | 27 August 2019, 12:12:46 UTC | Autogen: Fix AUTOUIC segfault, when file includes colliding ui_*.h file This fixes a case of use after move of a `std::shared_ptr` in `AUTOUIC`. It triggered a segfault, when the error message for colliding `ui_*.h` includes in different files was computed. | 27 August 2019, 14:17:33 UTC |
| 1d68639 | Brad King | 27 August 2019, 14:11:37 UTC | Merge branch 'alpine-cpu_zero' into release-3.15 Merge-request: !3740 | 27 August 2019, 14:11:37 UTC |
| 6157c0f | Brad King | 27 August 2019, 14:11:29 UTC | Merge branch 'cmGlobalGenerator-compilerId-lifetime' into release-3.15 Merge-request: !3741 | 27 August 2019, 14:11:29 UTC |
| dd6154c | Brad King | 27 August 2019, 14:11:16 UTC | Merge branch 'libarchive-requirement' into release-3.15 Merge-request: !3737 | 27 August 2019, 14:11:16 UTC |
| b0566f6 | Brad King | 27 August 2019, 14:11:06 UTC | Merge branch 'ninja_additional_clean_files_custom_target' into release-3.15 Merge-request: !3739 | 27 August 2019, 14:11:06 UTC |
| 1902e39 | Brad King | 26 August 2019, 13:26:00 UTC | cmAffinity: Add include for CPU_ZERO on Alpine Linux The definition of `CPU_ZERO` requires `<string.h>` to be included explicitly for `memset`. Since IWYU does not agree on other Linux platforms, use a pragma to silence the warning. Fixes: #19643 | 27 August 2019, 13:32:32 UTC |
| 17ce0c2 | Brad King | 26 August 2019, 14:25:54 UTC | cmGlobalGenerator: Fix CheckCompilerIdCompatibility local var lifetime Save the value of the compiler id variable in storage we own so that mutating it based on a policy does not invalidate the local value for later comparisons. This was identified by Clang AddressSanitizer. | 26 August 2019, 14:28:32 UTC |
| 752fa8b | Marvin Schmidt | 25 August 2019, 21:12:36 UTC | libarchive: We now require at least version 3.3.3 It's the first version including Zstandard support. | 26 August 2019, 13:47:24 UTC |
| d040f3f | Sebastian Holtermann | 26 August 2019, 10:48:27 UTC | Tests: Extend MakeClean test to test various target types This extends the MakeClean test to test the target property `ADDITIONAL_CLEAN_FILES` on executable, library and custom targets. | 26 August 2019, 13:31:03 UTC |
| 3ed8cff | Sebastian Holtermann | 26 August 2019, 09:47:27 UTC | Ninja: Add support for ADDITIONAL_CLEAN_FILES in custom targets This enables the support for `ADDITIONAL_CLEAN_FILES` in custom targets using the ninja generator. Fixes: #19641 | 26 August 2019, 13:31:03 UTC |
| 290ab79 | Brad King | 22 August 2019, 19:09:49 UTC | Merge branch 'ctest-json-REQUIRED_FILES' into release-3.15 Merge-request: !3719 | 22 August 2019, 19:09:49 UTC |
| 5778880 | Brad King | 22 August 2019, 19:00:38 UTC | CTest: Fix --show-only=json-v1 output with REQUIRED_FILES property Fixes: #19629 | 22 August 2019, 19:07:43 UTC |
| d911f8f | Brad King | 22 August 2019, 16:27:08 UTC | Merge branch 'CrayPrgEnv-update-link-type-detection' into release-3.15 Merge-request: !3716 | 22 August 2019, 16:27:08 UTC |
| 971c778 | Chuck Atkins | 22 August 2019, 15:55:43 UTC | CrayPrgEnv: Change default linking mode based on PE version Beginning with the 19.06 release of the Cray Programming Environment, the default linking mode on XC Cray systems is dynamic instead of static. This updates the CrayPrgEnv compiler wrappers to detect the PE version being used and behave accordingly. | 22 August 2019, 16:26:06 UTC |
| 9182b3c | Brad King | 21 August 2019, 14:10:52 UTC | Merge branch 'FindMPI-restore-flag-vars' into release-3.15 Merge-request: !3710 | 21 August 2019, 14:10:52 UTC |
| 31b8b28 | Robert Maynard | 20 August 2019, 21:38:53 UTC | FindMPI: Restore MPI_<LANG>_COMPILE_FLAGS and MPI_<LANG>_COMPILE_OPTIONS In commit e374b9f1eb (FindMPI: Restore MPI_<LANG>_COMPILE_FLAGS as a command-line string, 2018-09-10, v3.12.3~6^2) we tried to restore the compile flags but accidentally inverted the arguments to `list(JOIN)` causing both `MPI_<LANG>_COMPILE_FLAGS` and `MPI_<LANG>_COMPILE_OPTIONS` to be empty. Issue: #18349 | 21 August 2019, 14:08:12 UTC |
| feec57e | Brad King | 20 August 2019, 12:56:21 UTC | Merge branch 'ccmake-crash-on-empty-strings-property' into release-3.15 Merge-request: !3678 | 20 August 2019, 12:56:21 UTC |
| 154c5f7 | M Furkan USLU | 09 August 2019, 22:48:34 UTC | ccmake: handle cache entries with empty STRINGS property Fixes: #19585 | 20 August 2019, 12:48:09 UTC |
| ff7f8b8 | Brad King | 09 August 2019, 14:24:30 UTC | Merge branch 'msvc-runtime-library-flang' into release-3.15 Merge-request: !3674 | 09 August 2019, 14:24:30 UTC |
| ea0294c | Brad King | 09 August 2019, 13:55:05 UTC | Flang: Implement MSVC runtime library abstraction In commit fb3370b6a1 (MSVC: Add abstraction for runtime library selection, 2019-04-10, v3.15.0-rc1~229^2) we overlooked updating flags for Flang on Windows. Add them now and update the MSVCRuntimeLibrary Fortran test to work with Flang. Base the flags on those we already use for the GNU-like Clang targeting the MSVC ABI. Fixes: #19583 | 09 August 2019, 14:18:54 UTC |
| 40bbe50 | Brad King | 07 August 2019, 16:44:19 UTC | CMake 3.15.2 | 07 August 2019, 16:44:19 UTC |
| dfac85b | Brad King | 07 August 2019, 16:42:56 UTC | Merge branch 'doc-relnotes-3.15' into release-3.15 Merge-request: !3664 | 07 August 2019, 16:42:56 UTC |
| 18ce372 | Brad King | 07 August 2019, 16:41:27 UTC | Help: Add 3.15.2 release notes | 07 August 2019, 16:41:27 UTC |
| 1c7a4f9 | Brad King | 06 August 2019, 13:53:42 UTC | Merge branch 'FindGLEW-macOS' into release-3.15 Merge-request: !3656 | 06 August 2019, 13:53:42 UTC |
| feeb038 | Claudio Fantacci | 06 August 2019, 10:59:35 UTC | FindGLEW: Fix typo in verbose log message | 06 August 2019, 13:49:03 UTC |
| ab822a9 | Claudio Fantacci | 06 August 2019, 10:57:50 UTC | FindGLEW: Add required OpenGL dependency in macOS macOS requires OpenGL as INTERFACE_LINK_LIBRARIES dependency in the GLEW targets. This commit fixes this issue. | 06 August 2019, 13:49:03 UTC |
| a8a3efa | Claudio Fantacci | 06 August 2019, 10:55:52 UTC | FindGLEW: Fix macOS library suffix selection Fix logic added by commit a7d853868b (FindGLEW: Update implementation, 2019-03-13, v3.15.0-rc1~375^2~1) on macOS. macOS is recognized as both UNIX and APPLE. Consequently, the library suffix for shared and static library was set, respectively, as `.so` and `.a`, just like UNIX systems. Fix this by properly checking the OS type. Fixes: #19542 | 06 August 2019, 13:47:35 UTC |
| 9a384e7 | Brad King | 06 August 2019, 13:43:25 UTC | Merge branch 'find_package-prefer-config-not-found' into release-3.15 Merge-request: !3653 | 06 August 2019, 13:43:25 UTC |
| 8ed8686 | Cristian Adam | 05 August 2019, 21:46:54 UTC | find_package: Fix prefer-config mode to not fail on missing optional package When `CMAKE_FIND_PACKAGE_PREFER_CONFIG` mode was set to `ON`, failure to find a package was fatal even if it was not `REQUIRED`. Fix this and add a test case. Fixes: #19557 | 06 August 2019, 13:36:36 UTC |
| 1c3404a | Brad King | 05 August 2019, 14:28:29 UTC | Merge branch 'clang-frontend-variant' into release-3.15 Merge-request: !3650 | 05 August 2019, 14:28:29 UTC |
| a245479 | Brad King | 05 August 2019, 13:43:00 UTC | clang: Work around toolchain file use of internal CMake variables Since commit d44c0db0b2 (clang: setup correct configuration in gnu mode, 2019-02-20, v3.15.0-rc1~41^2~5) our Clang compiler information modules need the `CMAKE_<LANG>_COMPILER_FRONTEND_VARIANT` variable that we compute during compiler detection. However, some existing toolchain files set our internal `CMAKE_<LANG>_COMPILER_ID_RUN` variables and block that detection, but do not set the new frontend variant variable. Help them out by setting `CMAKE_<LANG>_COMPILER_FRONTEND_VARIANT` anyway. Fixes: #19515, #19539 | 05 August 2019, 13:43:00 UTC |
| edca8d5 | Brad King | 02 August 2019, 15:06:22 UTC | Merge branch 'fileapi-install-generators' into release-3.15 Merge-request: !3639 | 02 August 2019, 15:06:22 UTC |
| d70a0f8 | Brad King | 31 July 2019, 19:17:45 UTC | fileapi: Fix codemodel target install destination for cross-dir rules Since commit e89ad0f94e (install: Allow installing targets created in another directory, 2018-06-18, v3.13.0-rc1~407^2) we support calling `install(TARGETS)` for targets created in another directory. However, install generators are associated with the directory in which the call to `install()` appears. This may not be the same directory in which the target is defined. Record in each target the list of install generators it has. Fixes: #19546 | 31 July 2019, 23:32:55 UTC |
| 1ea751c | Brad King | 31 July 2019, 17:04:03 UTC | Merge branch 'clang-cl-non-windows' into release-3.15 Merge-request: !3634 | 31 July 2019, 17:04:03 UTC |
| 863f7eb | Brad King | 31 July 2019, 16:45:53 UTC | clang: Restore support for clang-cl on non-Windows hosts The frontend variant detection logic added by commit 53fbe23f3f (clang: introduce CMAKE_<lang>_COMPILER_FRONTEND_VARIANT, 2019-02-20, v3.15.0-rc1~41^2~8) assumes that `clang-cl` only runs on a Windows host. It is also available on non-Windows hosts. Fix the condition. Fixes: #19544 | 31 July 2019, 16:52:35 UTC |
| 7d98cd0 | Brad King | 30 July 2019, 15:31:15 UTC | Merge branch 'source_group-tree-files' into release-3.15 Merge-request: !3630 | 30 July 2019, 15:31:15 UTC |
| 93af8a2 | Brad King | 30 July 2019, 15:26:02 UTC | source_group: Fix regression in relative FILES Fix the check added in commit 8d93815d20 (source_group command ensures that FILES arguments are actually files, 2019-04-25, v3.15.0-rc1~195^2) to convert to an absolute path before checking for existence. Also simplify the conversion to an absolute path. Fixes: #19454 | 30 July 2019, 15:29:58 UTC |
| 4053d57 | Brad King | 30 July 2019, 15:20:59 UTC | Merge branch 'vs-spectre-off' into release-3.15 Merge-request: !3629 | 30 July 2019, 15:20:59 UTC |
| f9b7c66 | Brad King | 30 July 2019, 15:05:04 UTC | VS: Fix mapping of `-Qspectre-` flag The mapping for this flag was added by commit 43aa632f57 (VS: Populate `-Qspectre-` flag table entry for v142, 2019-01-24, v3.14.0-rc1~74^2~7). However, it did not do anything because the special logic added by commit bb60ed6e72 (VS: Add flag table entry for -Qspectre, 2018-10-08, v3.13.0-rc1~4^2) to move the `SpectreMitigation` element from `ClCompile` to the top level only handled the presence of the setting and not its value. Extend the special logic to carry the value too. Fixes: #19535 | 30 July 2019, 15:17:28 UTC |
| 055a782 | Brad King | 29 July 2019, 19:34:19 UTC | Merge branch 'swift-with-interface-libs' into release-3.15 Merge-request: !3624 | 29 July 2019, 19:34:19 UTC |
| 601fe84 | Brad King | 29 July 2019, 19:06:27 UTC | Swift: Restore support for enabling with INTERFACE libraries The check added in commit b06f4c8a74 (Swift: disallow WIN32_EXECUTABLE properties, 2019-05-31, v3.15.0-rc1~9^2) makes sense only for executables because the `WIN32_EXECUTABLE` property is defined only for them. Running the check on other target types, particularly those that do not link such as INTERFACE libraries, violates internal assumptions. In particular, `GetLinkerLanguage` should not be called on such targets. Fixes: #19528 | 29 July 2019, 19:24:29 UTC |
| f43a7d7 | Brad King | 26 July 2019, 11:50:55 UTC | CMake 3.15.1 | 26 July 2019, 11:50:55 UTC |
| 838278f | Brad King | 26 July 2019, 11:25:33 UTC | Merge branch 'doc-relnotes-3.15' into release-3.15 Merge-request: !3608 | 26 July 2019, 11:25:33 UTC |
| 3b113cc | Brad King | 25 July 2019, 21:07:23 UTC | Help: Add 3.15.1 release notes | 26 July 2019, 11:18:09 UTC |
| 693a9b3 | Brad King | 25 July 2019, 17:09:25 UTC | Merge branch 'FindMPI-link-flags' into release-3.15 Merge-request: !3605 | 25 July 2019, 17:09:25 UTC |
| cf04da7 | Robert Maynard | 25 July 2019, 16:00:50 UTC | FindMPI: make sure computed link flags are not de-duplicated In commit f7eaa342de (FindMPI: Store imported target link flags as a list instead of a string, 2019-06-14, v3.15.0-rc2~2^2) we used `separate_arguments` to parse the extracted link flags and add them to `INTERFACE_LINK_LIBRARIES`. That property is not meant for link flags and CMake may de-duplicate them. This is particularly problematic for flags like `-Wl,-rpath -Wl,/path1 -Wl,-rpath -Wl,/path2`. In commit 39c572c9c9 (FindMPI: Updated to use INTERFACE_LINK_OPTIONS, 2019-06-24) we moved the parsed flags over to `INTERFACE_LINK_OPTIONS`, but that may still perform de-duplication. Avoid the parsing and de-duplication of flags by passing the original string via `SHELL:` instead. Fixes: #19516 | 25 July 2019, 16:59:21 UTC |
| 070a5e3 | Brad King | 25 July 2019, 11:15:42 UTC | Merge branch 'makefile-depend-relative-include' into release-3.15 Merge-request: !3599 | 25 July 2019, 11:15:42 UTC |
| d46bac5 | Brad King | 24 July 2019, 13:53:53 UTC | Makefile: Fix regression in dependencies on relative includes Since commit a13a5c948e (Replace use of CollapseCombinedPath with CollapseFullPath, 2019-03-19, v3.15.0-rc1~361^2~1), one code path now calls `CollapseFullPath` with a base path that may be relative. Backport KWSys commit c6f8e24a3 (SystemTools: Fix CollapseFullPath with relative base path, 2019-07-24) to handle such base paths. This case occurs when a build tree is placed in a directory inside a source tree such that CMake is willing to generate a relative path from the build tree to the source tree. Add a test covering this case. Fixes: #19507 | 24 July 2019, 15:37:31 UTC |
| 420073e | Brad King | 24 July 2019, 12:12:51 UTC | Merge branch 'backport-clang-gnulike-support' into release-3.15 Merge-request: !3592 | 24 July 2019, 12:12:51 UTC |
| 4f15a6a | Brad King | 24 July 2019, 11:29:21 UTC | Tests: Revert "require C++14 for the Tutorial" Revert commit a2a90f41e3 (Tests: require C++14 for the Tutorial, 2019-03-21, v3.15.0-rc1~41^2~2). In commit d50b31be35 (Clang: For MSVC ABI do not use modes older than C++14, 2019-07-23) we fixed the C++ standard selection for GNU-like Clang with the MSVC ABI so the test code itself no longer needs to do it. In particular, changing the tests in this way broke the tutorial's narrative. | 24 July 2019, 12:02:37 UTC |
| d50b31b | Brad King | 23 July 2019, 12:50:30 UTC | Clang: For MSVC ABI do not use modes older than C++14 Since commit d44c0db0b2 (clang: setup correct configuration in gnu mode, 2019-02-20, v3.15.0-rc1~41^2~5) we support the GNU-like Clang that targets the MSVC ABI. However, Clang cannot compile with the MSVC standard library unless it runs in a mode aware of C++14 (since MSVC itself does not even have a lower mode). When `CMAKE_CXX_STANDARD` is set to 98 or 11, use C++14 anyway. Since Clang's default mode is aware of C++14, another option is to not add any flags for 98 or 11. However, if a future Clang version ever defaults to a higher C++ standard, setting the standard to 98 or 11 should at least not use a mode higher than 14. Also revert test updates from commit 4819ff9647 (Tests: fix failures with gnu mode clang on windows, 2019-03-21, v3.15.0-rc1~41^2~3) that were meant to work around the standard selection problem. Fixes: #19496 | 24 July 2019, 11:40:30 UTC |
| 07b93cb | Brad King | 23 July 2019, 12:38:57 UTC | Merge branch 'fix-emulator-arguments' into release-3.15 Merge-request: !3591 | 23 July 2019, 12:38:57 UTC |
| bf6f546 | Marek Antoniak | 22 July 2019, 07:46:48 UTC | Fix allocation in CROSSCOMPILING_EMULATOR evaluation In commit fec441ec17 (Teach CROSSCOMPILING_EMULATOR to support arguments, 2019-05-30, v3.15.0-rc1~6^2) the new member `cmCustomCommandGenerator::EmulatorsWithArguments` was not initialized to the proper size. Fix this and add a test case covering the crash that could occur with multiple commands where an emulator appears only in a later command. Fixes: #19500 Co-Author: Brad King <brad.king@kitware.com> | 23 July 2019, 12:33:31 UTC |
| 4cac01c | Brad King | 22 July 2019, 14:20:06 UTC | Merge branch 'InstallRequiredSystemLibraries-redist' into release-3.15 Merge-request: !3585 | 22 July 2019, 14:20:06 UTC |
| 13c3ec5 | James Butler | 20 July 2019, 21:27:50 UTC | IRSL: Fix discovery of VS 2019 v141 toolset redistributables Since VS 2019, the v141 toolset redistributables can be found in either the VS 2019 or VS 2017 install directory. Update the logic to search multiple versions of VS. Fixes: #19488 | 22 July 2019, 14:06:45 UTC |
| 0484165 | James Butler | 21 July 2019, 02:15:26 UTC | IRSL: Fix typo in v143 toolset version check Fix the toolset v143 check from commit 33ee779330 (IRSL: Fix discovery of VS 2019 v142 toolset redistributables, 2019-04-03, v3.14.2~6^2) to check the correct variable. | 22 July 2019, 14:06:44 UTC |
