| 3c9dec0 | Brad King | 29 March 2019, 13:22:46 UTC | CMake 3.14.1 | 29 March 2019, 13:22:46 UTC |
| 30159fe | Brad King | 29 March 2019, 12:49:34 UTC | Merge branch 'implicit-includes' into release-3.14 Merge-request: !3157 | 29 March 2019, 12:49:34 UTC |
| dad86f1 | Brad King | 27 March 2019, 14:09:22 UTC | ParseImplicitIncludeInfo: Canonicalize implicit include dirs The implicit include directory extraction added by commit 5990ecb741 (Compute implicit include directories from compiler output, 2018-12-07, v3.14.0-rc1~108^2) leaves paths like `/usr/lib/../include` unchanged. Fix the logic to canonicalize such paths (e.g. to `/usr/include`) as we do for implicit link directories already. This is important to ensure the set of implicit directories is represented in the same form as the include directories that will be compared to them. Issue: #19095 | 29 March 2019, 12:48:56 UTC |
| 04c0efd | Brad King | 29 March 2019, 12:48:39 UTC | Merge branch 'implicit-includes-autogen' into release-3.14 Merge-request: !3159 | 29 March 2019, 12:48:39 UTC |
| bd00090 | Brad King | 29 March 2019, 12:48:28 UTC | Merge branch 'ifw_group_option_parsing' into release-3.14 Merge-request: !3160 | 29 March 2019, 12:48:28 UTC |
| 6f6e096 | Clément Rezvoy | 28 March 2019, 17:21:30 UTC | CPackIFW: Add missing cpack_ifw_configure_component_group option processing Both commit 88ecfd8ba1 (CPackIFW: Add some options, 2016-11-11, v3.8.0-rc1~248^2) and commit e5089c562c (CPackIFW: Add some options, 2017-01-24, v3.8.0-rc1~53^2) added some options to this macro's documentation and implementation, but the actual processing of the parsed options was never added. Add it now. Reviewed-by: Konstantin Podsvirov <konstantin@podsvirov.pro> | 28 March 2019, 18:59:08 UTC |
| a8b7cbb | Sebastian Holtermann | 28 March 2019, 09:00:40 UTC | Autogen: Do not treat hard-coded -I/usr/include exclusion as implicit include The `cmLocalGenerator::GetIncludeDirectoriesImplicit` method is called by `cmQtAutoGenInitializer` to get the compiler's list of implicit include directories. Since commit 557b2d6e65 (Fix regression in -I/usr/include exclusion logic, 2019-02-13, v3.14.0-rc2~6^2~2) the method hard-codes exclusion of `/usr/include` for historical reasons. However, it should not be reported as a real implicit include directory unless the compiler really has it. Refactor the logic to distinguish the hard-coded exclusion of `/usr/include` from the real list of implicit include directories. Fixes: #19100 | 28 March 2019, 18:07:24 UTC |
| 52bb176 | Brad King | 27 March 2019, 18:22:52 UTC | Merge branch 'backport-kwsys-SystemTools-copy-self' into release-3.14 Merge-request: !3145 | 27 March 2019, 18:22:52 UTC |
| 97c163f | Brad King | 27 March 2019, 18:20:53 UTC | Merge branch 'FindFontconfig-var-case' into release-3.14 Merge-request: !3153 | 27 March 2019, 18:20:53 UTC |
| 9cf64bb | Brad King | 27 March 2019, 18:20:45 UTC | Merge branch 'jacoco_parser_crash' into release-3.14 Merge-request: !3147 | 27 March 2019, 18:20:45 UTC |
| a3a1e69 | Brad King | 26 March 2019, 17:44:52 UTC | FindFontconfig: Convert module variables to camel case Our documented standard for find module variable names is to match the case of the find module package name. This was overlooked when the module was added by commit 84e7920b3a (FindFontconfig: Add module to find Fontconfig, 2018-09-27, v3.14.0-rc1~523^2). The module was released with the upper case names in CMake 3.14.0, so fix it to have camel case names in 3.14.1. This is incompatible but anyone using a given release series should be using the latest patch on it and we've made breaking fixups on newly released features like this before. Reported-by: Christophe Giboudeaux <christophe@krop.fr> Fixes: #19094 | 26 March 2019, 18:14:09 UTC |
| 1d16eae | Sylvain Joubert | 26 March 2019, 09:52:57 UTC | ctest_coverage: fix out-of-bounds index in Jacoco parser When the current source file is not found the FilePath variable was left with the previous path content. In case the previous file had less lines than the current one and there are 'line' entries for the current one with higher number we ended up in a buffer overflow while indexing the previous file entry with a line number higher. By clearing the FilePath, the empty() guard triggers correctly on an empty path and it avoid modifying the wrong data. | 26 March 2019, 15:50:30 UTC |
| 505bdd3 | Brad King | 26 March 2019, 14:58:08 UTC | Merge branch 'cuda-bracket-output' into release-3.14 Merge-request: !3151 | 26 March 2019, 14:58:08 UTC |
| ce180cf | Brad King | 25 March 2019, 18:24:41 UTC | cmake: Fix '-E copy foo .' to avoid clobbering file Backport KWSys commit 92334e7670 (SystemTools: CopyFileAlways: avoid copying file over self, 2019-03-25) to the CMake 3.14 release branch. Fixes: #19075 | 26 March 2019, 14:51:47 UTC |
| b127e0c | Brad King | 26 March 2019, 14:40:11 UTC | CUDA: Tolerate square brackets in PROMPT environment variable The `PROMPT` environment variable affects nvcc's output. Fix our parsing of that output to tolerate square brackets. Fixes: #19089 | 26 March 2019, 14:43:51 UTC |
| c22a2b4 | Brad King | 25 March 2019, 15:50:06 UTC | Merge branch 'toolchain-include_directories' into release-3.14 Merge-request: !3140 | 25 March 2019, 15:50:06 UTC |
| 588fa1b | Brad King | 22 March 2019, 19:39:03 UTC | Restore support for include_directories() in toolchain files Any `include_directories()` calls in toolchain files are used during our ABI detection step even though it does not include any system headers. Since commit 5990ecb741 (Compute implicit include directories from compiler output, 2018-12-07, v3.14.0-rc1~108^2), that check is also used to detect implicit include directories. Any `include_directories()` in a toolchain file are detected as implicit and later excluded from explicit specification on compiler command lines, thus breaking the purpose of the calls in the first place. Fix the implicit include directory detection step to avoid using paths from `include_directories()` calls in the toolchain file. Fixes: #19079 | 25 March 2019, 15:48:17 UTC |
| b743058 | Brad King | 21 March 2019, 12:56:39 UTC | Merge branch 'doc-cmp0082' into release-3.14 Merge-request: !3133 | 21 March 2019, 12:56:39 UTC |
| ce730e9 | Brad King | 21 March 2019, 12:51:35 UTC | Help: Clarify policy CMP0082 documentation The policy documentation added by commit fc8955e889 (add_subdirectory: Run subdirectory install rules in correct order, 2018-10-02, v3.14.0-rc1~565^2~1) left out our usual sentence about the policy providing compatibility. | 21 March 2019, 12:55:28 UTC |
| 8cc16c9 | Brad King | 20 March 2019, 15:22:02 UTC | Merge branch 'armcc-compiler-id' into release-3.14 Merge-request: !3127 | 20 March 2019, 15:22:02 UTC |
| 8f8d056 | Brad King | 20 March 2019, 15:12:27 UTC | ARMCC: Fix identification of ARM compiler when it defines GNU macros According to ARMCC 5.06 documentation: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0472m/chr1359125007083.html the compiler may define `__GNUC__` in addition to `__ARMCC_VERSION`. Re-order our preprocessor checks to consider the ARM-specific macro first so that the ARM compiler is not mistaken for a GNU compiler. Fixes: #19065 | 20 March 2019, 15:20:39 UTC |
| 9603e41 | Brad King | 20 March 2019, 14:54:24 UTC | Merge branch 'eclipse-interface-lib' into release-3.14 Merge-request: !3125 | 20 March 2019, 14:54:24 UTC |
| d3dcf8d | Brad King | 20 March 2019, 14:48:28 UTC | Eclipse: Fix extra generator to not crash on interface libraries Do not process interface libraries in ways that expect build information to be present internally. This filtering was left out of the extra generator accidentally when interface libraries were introduced, but it worked by accident until commit 76ad2ecb50 (Order SYSTEM include directories after non-system directories, 2018-04-13, v3.12.0-rc1~179^2) added a code path that was not tolerated. Fixes: #18363 | 20 March 2019, 14:52:31 UTC |
| 5b6c6c2 | Brad King | 14 March 2019, 18:52:12 UTC | Merge branch 'find_program-windows-share' into release-3.14 Merge-request: !3105 | 14 March 2019, 18:52:12 UTC |
| 00c4ddf | Brad King | 14 March 2019, 18:34:37 UTC | find_program: Restore leading double slash on Windows network path Since commit c76c1ea208 (find_program: Consider CWD only for paths with separator, 2018-05-31, v3.13.0-rc1~413^2) we accidentally convert the leading `//` to just `/` on results with Windows network paths. This was caused by `CollapseCombinedPath` being less robust than `CollapseFullPath`. Restore use of the latter but in a way that preserves the requirement of the above commit to support candidates that are themselves absolute. Fixes: #19049 Issue: #19050 | 14 March 2019, 18:46:23 UTC |
| 0e652f2 | Brad King | 14 March 2019, 18:01:02 UTC | Merge branch 'FindPython-ensure-correct-architecture-selected' into release-3.14 Merge-request: !3103 | 14 March 2019, 18:01:02 UTC |
| 9a84cb1 | Marc Chevrier | 14 March 2019, 17:40:22 UTC | FindPython*: ensure correct architecture is selected. Ensure interpreter and libraries architecture matches CMake build configuration. Update documentation about interpreter constraints. Fixes: #19024 | 14 March 2019, 17:53:57 UTC |
| b5b2415 | Brad King | 14 March 2019, 17:24:25 UTC | Merge branch 'vs2019-wow64' into release-3.14 Merge-request: !3102 | 14 March 2019, 17:24:25 UTC |
| 5c50eea | Brad King | 14 March 2019, 17:14:23 UTC | VS: Fix x64 host recognition by x86 cmake process In commit 57e48f16f2 (VS: Add Visual Studio 16 2019 generator, 2019-01-09, v3.14.0-rc1~150^2) and commit 0fd742a6ff (VS: Teach VS 2019 generator to select host tools matching host arch, 2019-01-28, v3.14.0-rc1~63^2) we intended to select the `x64` target architecture and `x64` host tools by default on x64 host machines. Fix detection of a x64 host when CMake itself is a 32-bit x86 process. The KWSys SystemInformation `Is64Bits` member is not set correctly, which led to this bug. Pending investigation on the KWSys side, simply test ourselves via `IsWow64Process`. | 14 March 2019, 17:19:18 UTC |
| bf02d62 | Brad King | 14 March 2019, 13:08:05 UTC | CMake 3.14.0 | 14 March 2019, 13:08:05 UTC |
| 1b6a304 | Brad King | 12 March 2019, 17:01:57 UTC | Merge branch 'revert-vs-msbuild-arch' into release-3.14 Merge-request: !3090 | 12 March 2019, 17:01:57 UTC |
| f3cedf3 | Brad King | 12 March 2019, 16:53:06 UTC | VS: Revert "Use MSBuild matching toolset host architecture" Revert commit da402a081b (VS: Use MSBuild matching toolset host architecture, 2019-01-28, v3.14.0-rc1~50^2). Multiple people have reported that the 64-bit `amd64/msbuild` tool fails in cases that the 32-bit `msbuild` works. Drop our change pending further investigation and hopefully a fix to VS. Fixes: #18904, #19037 Issue: #18219 | 12 March 2019, 16:53:06 UTC |
| 225675b | Brad King | 12 March 2019, 13:41:37 UTC | Merge branch 'wix-cmake-downgrade-fix' into release-3.14 Merge-request: !3087 | 12 March 2019, 13:41:37 UTC |
| 7593bdf | Nils Gladitz | 12 March 2019, 07:58:45 UTC | CMake: Fix WiX installer downgrades with versioned binaries Since commit 5b9da05b7a (Windows: Embed version information into CMake binaries, 2017-10-25, v3.11.0-rc1~411^2) our binaries have version information that prevents a `.msi` downgrade from replacing them by default. Configure the re-install mode: * a: reinstall all files regardless of version * m: rewrite all per-machine registry entries * u: rewrite all per-user registry entries * s: reinstall shortcuts and icons Fixes: #19006 | 12 March 2019, 13:39:35 UTC |
| f96f1aa | Brad King | 08 March 2019, 12:34:57 UTC | CMake 3.14.0-rc4 | 08 March 2019, 12:34:57 UTC |
| 0e2804b | Brad King | 07 March 2019, 20:00:26 UTC | Merge branch 'cxx-checks-warning-match' into release-3.14 Merge-request: !3075 | 07 March 2019, 20:00:26 UTC |
| 4ca5a81 | Brad King | 07 March 2019, 19:55:54 UTC | C++ feature checks: Match warnings more strictly Require the word "warning" to appear at the start of a line, after whitespace, or after a `:`. This is the same that CTest launchers use to match warnings. It avoids matching "warning" inside file paths. Fixes: #19019 | 07 March 2019, 19:55:54 UTC |
| c042c99 | Brad King | 07 March 2019, 14:17:21 UTC | Merge branch 'install-no-imported-global' into release-3.14 Merge-request: !3071 | 07 March 2019, 14:17:21 UTC |
| 47389c5 | Brad King | 07 March 2019, 13:52:18 UTC | install: Do not crash on imported global target Since commit e89ad0f94e (install: Allow installing targets created in another directory, 2018-06-18, v3.13.0-rc1~407^2) the `install(TARGETS)` command may find a global-scoped target outside the calling directory. Ignore an `IMPORTED GLOBAL` target if it is found in this way. Imported targets cannot be installed, and trying to do so violates internal invariants. Fixes: #19022 | 07 March 2019, 14:00:56 UTC |
| 898d21e | Brad King | 06 March 2019, 14:43:27 UTC | Merge branch 'vs-explicit-newline' into release-3.14 Merge-request: !3065 | 06 March 2019, 14:43:27 UTC |
| 0bf4418 | Luca Cappa | 05 March 2019, 19:08:09 UTC | VS: Encode newlines in XML attributes Encode `\n` as ` ` to avoid generating a literal newline inside an XML attribute. This is more readable and also fixes custom commands in `.csproj` files with VS 2019 RC. Fixes: #19001 | 06 March 2019, 14:37:21 UTC |
| ef10c9a | Brad King | 06 March 2019, 14:07:29 UTC | Merge branch 'docs-xcode-schemes' into release-3.14 Merge-request: !3066 | 06 March 2019, 14:07:29 UTC |
| d0cb912 | Craig Scott | 06 March 2019, 13:00:09 UTC | Help: Remove note that Xcode scheme generator is experimental | 06 March 2019, 13:04:55 UTC |
| de850fe | Craig Scott | 06 March 2019, 12:57:45 UTC | Help: Trivial typo fix for CMAKE_XCODE_GENERATE_SCHEME | 06 March 2019, 13:04:55 UTC |
| d61a5a2 | Craig Scott | 06 March 2019, 12:38:56 UTC | Help: Sort lists of (CMAKE_)XCODE_SCHEME_... variables and properties | 06 March 2019, 13:04:55 UTC |
| ec79045 | Brad King | 05 March 2019, 16:26:34 UTC | Merge branch 'docs-install-destinations' into release-3.14 Merge-request: !3052 | 05 March 2019, 16:26:34 UTC |
| 216fff2 | Brad King | 05 March 2019, 14:46:40 UTC | Merge branch 'ios-docs' into release-3.14 Merge-request: !3047 | 05 March 2019, 14:46:40 UTC |
| 376138f | Ruslan Baratov | 01 March 2019, 16:48:21 UTC | Help: CMAKE_MACOSX_BUNDLE is ON for iOS/tvOS/watchOS | 05 March 2019, 14:45:50 UTC |
| f7d602b | Ruslan Baratov | 01 March 2019, 15:38:20 UTC | Help: Example of tweaking iOS/tvOS/watchOS build CMAKE_OSX_ARCHITECTURES and CMAKE_OSX_DEPLOYMENT_TARGET variables can be used to tweak iOS/tvOS/watchOS build | 05 March 2019, 14:45:50 UTC |
| 4a9e2e4 | Ruslan Baratov | 01 March 2019, 16:16:36 UTC | Help: find_package with fat iOS libraries | 05 March 2019, 14:45:50 UTC |
| 509a940 | Brad King | 05 March 2019, 14:42:58 UTC | Merge branch 'ios-variable' into release-3.14 Merge-request: !3051 | 05 March 2019, 14:42:58 UTC |
| e427c7c | Ruslan Baratov | 01 March 2019, 18:08:03 UTC | iOS: Add IOS variable Since commit 11da882a12 (Apple: Introduce separate system name for iOS, tvOS, and watchOS, 2018-01-15, v3.14.0-rc1~14^2~1) we support setting `CMAKE_SYSTEM_NAME` to `iOS`. Existing iOS toolchain files already set `IOS` as a short-hand variable, so do the same here. | 05 March 2019, 14:42:41 UTC |
| a5f79b8 | Craig Scott | 02 March 2019, 10:46:48 UTC | Help: clarify DESTINATION and TYPE usage for install() | 05 March 2019, 10:48:44 UTC |
| 5c0ef41 | Brad King | 04 March 2019, 13:28:56 UTC | Merge branch 'FindPython-NumPy-fix-include-dir' into release-3.14 Merge-request: !3053 | 04 March 2019, 13:28:56 UTC |
| 8e33583 | Marc Chevrier | 02 March 2019, 14:52:12 UTC | FindPython: Fix NumPy component include directory Update the component added by commit 513e77550d (FindPython: Introduce NumPy component, 2018-12-12, v3.14.0-rc1~95^2). The `numpy/` sub-directory should not be part of the include directory. It should be part of the `#include` line. | 04 March 2019, 13:28:21 UTC |
| 77439d9 | Brad King | 01 March 2019, 17:02:31 UTC | Merge branch 'vs-fortran-rc' into release-3.14 Merge-request: !3050 | 01 March 2019, 17:02:31 UTC |
| 0b82f56 | Brad King | 01 March 2019, 16:47:34 UTC | VS: Fix Fortran target type selection with RC sources The Intel Fortran `.vfproj` files do support both Fortran and the Windows Resource compiler (`.rc)` files. Prior to CMake 3.9 we did not support that, but commit 2c9f35789d (VS: Decide project type by linker lang as fallback, 2017-03-30, v3.9.0-rc1~340^2) accidentally enabled it. It was then broken by commit d3d2c3cd49 (VS: Fix Fortran target type selection when linking C++ targets, 2019-02-04, v3.14.0-rc1~13^2). Restore support for Fortran+RC in VS projects and add a test case. Fixes: #19002 | 01 March 2019, 16:58:21 UTC |
| 20a41aa | Brad King | 01 March 2019, 14:25:27 UTC | CMake 3.14.0-rc3 | 01 March 2019, 14:25:27 UTC |
| 8d9cf29 | Brad King | 01 March 2019, 14:05:57 UTC | Merge branch 'findjni-paths' into release-3.14 Merge-request: !3042 | 01 March 2019, 14:05:57 UTC |
| 77cede0 | Christian Pfeiffer | 27 February 2019, 15:50:56 UTC | FindJNI: Unify path search, fix support for Java 9 Java 9 restructured the standard location of the AWT libraries due to the removal of the JRE/JDK separation. We should check all possible combinations of subdirectories to the Java root directories to ensure that the libraries will be found after an upgrade. Furthermore, a root directory would contain both, include and library paths, so the search should be unified to ease maintenance on the module. | 01 March 2019, 13:53:26 UTC |
| 9a54159 | Brad King | 01 March 2019, 13:02:26 UTC | Merge branch 'ExternalProject-fix-log-in-custom-stamp' into release-3.14 Merge-request: !3045 | 01 March 2019, 13:02:26 UTC |
| 338e32b | Brad King | 01 March 2019, 13:02:11 UTC | Merge branch 'cuda_device_link_handle_frameworks' into release-3.14 Merge-request: !3039 | 01 March 2019, 13:02:11 UTC |
| a6d3fee | Brad King | 01 March 2019, 12:54:17 UTC | ExternalProject: Restore default log dir with custom stamp dir In commit b6f6cac378 (ExternalProject: add LOG_DIR option that allows overriding of log location, 2018-10-12, v3.14.0-rc1~515^2~1) the log directory got its own option. The intention was to fall back to the stamp directory by default. However, the implementation actually only falls back to the same default as the stamp directory and does not consider a custom stamp dir. Update the default log dir computation to fall back to whatever is the final selection for the stamp dir. Fixes: #19000 | 01 March 2019, 12:54:17 UTC |
| d5d1b15 | Robert Maynard | 27 February 2019, 22:37:17 UTC | CUDA: Filter out -framework arguments during device linking The filter in commit e768d96c74 (CUDA: Filter out host link flags during device linking, 2018-10-22, v3.13.0-rc2~4^2~2^2) removes `-framework` but not the framework name that comes after it. Revise the logic to remove both. Fixes: #18911 | 28 February 2019, 19:56:11 UTC |
| 71852e9 | Brad King | 28 February 2019, 18:25:51 UTC | Merge branch 'vs2019' into release-3.14 Merge-request: !3044 | 28 February 2019, 18:25:51 UTC |
| c9a7f31 | Brad King | 28 February 2019, 16:05:31 UTC | Help: Update VS 2019 generator release note for preview 4 | 28 February 2019, 16:05:31 UTC |
| 00c1120 | Brad King | 28 February 2019, 16:02:53 UTC | VS: Drop workaround needed only for VS 2019 preview 2 and 3 A temporary workaround added by commit 626c51f47b (VS: Update for Visual Studio 2019 Preview 2, 2019-01-24, v3.14.0-rc1~74^2) is no longer needed as of VS 2019 preview 4. Fixes: #18898 | 28 February 2019, 16:04:29 UTC |
| 18731d6 | Brad King | 27 February 2019, 16:32:31 UTC | Merge branch 'backport-check-std-size-cbegin-cend' into release-3.14 Merge-request: !3030 | 27 February 2019, 16:32:31 UTC |
| e17deb7 | Mathieu Garaud | 27 February 2019, 14:47:41 UTC | Extend C++17/C++14 feature checks to cover more standard library APIs Make sure `std::cbegin`, `std::cend`, and `std::size` work in C++17 or C++14 mode before choosing the corresponding standard level for compiling CMake itself. This helps in cases that the compiler is using a standard library too old to support the full standard level chosen. | 27 February 2019, 16:24:43 UTC |
| e0d7078 | Brad King | 27 February 2019, 14:04:03 UTC | Merge branch 'FindThreads-revert-libc-check' into release-3.14 Merge-request: !3022 | 27 February 2019, 14:04:11 UTC |
| f369d59 | Brad King | 27 February 2019, 13:05:55 UTC | Merge branch 'cmake_role-vs-fix' into release-3.14 Merge-request: !3028 | 27 February 2019, 13:05:55 UTC |
| c2c7b96 | Brad King | 27 February 2019, 12:59:19 UTC | Merge branch 'docs-rpath-origin-apple' into release-3.14 Merge-request: !3020 | 27 February 2019, 12:59:19 UTC |
| e994e1f | Brad King | 27 February 2019, 12:57:03 UTC | Merge branch 'FindOctave-remove' into release-3.14 Merge-request: !3027 | 27 February 2019, 12:57:03 UTC |
| 624ce2c | Brad King | 27 February 2019, 12:56:11 UTC | Merge branch 'include_external_msproject-exclude-from-all' into release-3.14 Merge-request: !3025 | 27 February 2019, 12:56:11 UTC |
| 5833739 | Brad King | 27 February 2019, 12:55:28 UTC | Merge branch 'vs-llvm-extension' into release-3.14 Merge-request: !3024 | 27 February 2019, 12:55:28 UTC |
| 4570b5a | Brad King | 27 February 2019, 12:54:49 UTC | Merge branch 'restore-min-cmake-3.1' into release-3.14 Merge-request: !3021 | 27 February 2019, 12:54:49 UTC |
| 1832023 | Brad King | 27 February 2019, 12:28:05 UTC | FindThreads: Revert libc symbol check to pthread_create Since commit e9a1ddc594 (FindThreads: Replace the pthread symbol checking in libc., 2018-11-18, v3.14.0-rc1~292^2) we check libc for `pthread_kill` instead of `pthread_create`. However, on FreeBSD `pthread_kill` is in libc but not `pthread_create`. Discussion in the original merge request for the above commit also considered `pthread_key_create`, `pthread_self`, and `pthread_attr_init`. Every symbol seems to have some reason it is not an appropriate choice. Revert to the pre-3.14 behavior of using `pthread_create` pending further investigation. | 27 February 2019, 12:33:31 UTC |
| bf10f02 | Craig Scott | 26 February 2019, 11:43:46 UTC | Help: Fix minor inaccuracies of what BUILD_RPATH_USE_ORIGIN affects | 27 February 2019, 10:07:36 UTC |
| 4b95e7f | Kyle Edwards | 26 February 2019, 19:48:13 UTC | CMAKE_ROLE: Fix value in --build for Visual Studio generators Fixes: #18990 | 26 February 2019, 19:52:17 UTC |
| 7a1f3fe | Brad King | 26 February 2019, 19:12:34 UTC | FindOctave: Remove module pending further work The `FindOctave` module added by commit 170bcb6fdc (FindOctave: Add module to find GNU octave, 2018-11-17, v3.14.0-rc1~283^2) has a few problems in its implementation that need to be worked out before the module can be included in a CMake release. These were missed during review. Remove the module for now. It can be restored later with a fresh review. Issue: #18991 | 26 February 2019, 19:12:34 UTC |
| 3106cf4 | Brad King | 26 February 2019, 15:10:33 UTC | include_external_msproject: Restore support for EXCLUDE_FROM_ALL In commit dc6888573d (Pass EXCLUDE_FROM_ALL from directory to targets, 2019-01-15, v3.14.0-rc1~83^2) all `AddNewTarget` call sites were updated to copy the directory-level `EXCLUDE_FROM_ALL` into the target property of the same name, except that the one for `include_external_msproject` was incorrectly missed. Add it now. Furthermore, refactoring in commit b99129d2d8 (ENH: some code cleanup, 2007-03-12, v2.6.0~2020) accidentally set the `EXCLUDE_FROM_ALL` target property of `include_external_msproject`-generated targets to `FALSE` instead of simply leaving it unset. This was not necessary but had no effect until the above commit gave it a meaning. Drop that. Fixes: #18986 | 26 February 2019, 15:20:01 UTC |
| 8375c30 | Brad King | 26 February 2019, 14:49:55 UTC | VS: Fix detection of clang-cl with -T llvm When using a VS generator with `-T llvm`, MSBuild relies on the "LLVM Compiler Toolchain" VS Extension. This does not put `clang-cl` in the `PATH` inside the build, and LLVM no longer provides a `cl` replacement either. Therefore we need another way to extract the path to the `CMAKE_{C,CXX}_COMPILER`. Fortunately the LLVM VS integration provides a `$(ClangClExecutable)` macro we can reference to get the path. Fixes: #18983 | 26 February 2019, 14:58:51 UTC |
| e0267eb | Brad King | 26 February 2019, 12:46:26 UTC | FindThreads: Fix libc check to use proper header for pthread_kill In commit e9a1ddc594 (FindThreads: Replace the pthread symbol checking in libc., 2018-11-18, v3.14.0-rc1~292^2) we switched to checking for `pthread_kill` in libc but did not update the symbol check's header file to match. Add `signal.h` to get `pthread_kill`. Keep `pthread.h` anyway since the purpose of the check is to verify that the pthread API works. Fixes: #18984 | 26 February 2019, 12:51:52 UTC |
| 8455e16 | Brad King | 26 February 2019, 12:39:11 UTC | Merge branch 'doc-ctest-build-and-test-summary' into release-3.14 Merge-request: !3017 | 26 February 2019, 12:39:11 UTC |
| 02ba5d5 | Paul Seyfert | 25 February 2019, 11:31:44 UTC | Help: Fix --build-and-test synopsis in ctest(1) The synopsis added by commit 9d3aa95ca4 (Help: Divide ctest(1) manual options into sections, 2017-11-08, v3.11.0-rc1~359^2~2) is missing the actual `--build-and-test` argument! Add it now. | 26 February 2019, 12:37:29 UTC |
| a0d4430 | Brad King | 26 February 2019, 12:18:43 UTC | Tests: Restore support for CMake 3.1 through 3.6 with MSVC The change in commit a5dd159990 (Tests: Fix RunCMake.try_compile CxxStandard case on MSVC, 2017-09-22, v3.10.0-rc1~63^2) introduced use of `if()` conditions not supported until CMake 3.7, so while it was intended to restore support for CMake versions prior to 3.9, it actually only did so for 3.7 and 3.8. Backport the logic to work with CMake 3.1. Fixes: #18987 | 26 February 2019, 12:35:24 UTC |
| 4d337be | Brad King | 25 February 2019, 14:33:25 UTC | Merge branch 'qcc-asm-detection' into release-3.14 Merge-request: !3016 | 25 February 2019, 14:33:25 UTC |
| af000ab | Brad King | 25 February 2019, 12:54:25 UTC | Merge branch 'releasenotes_arch_independent' into release-3.14 Merge-request: !3012 | 25 February 2019, 12:54:25 UTC |
| 0e8b0ae | Brad King | 25 February 2019, 12:54:04 UTC | Merge branch 'docs_try_commands' into release-3.14 Merge-request: !3013 | 25 February 2019, 12:54:04 UTC |
| b3b081c | Brad King | 25 February 2019, 12:53:49 UTC | Merge branch 'check_lang_source_runs_output' into release-3.14 Merge-request: !3011 | 25 February 2019, 12:53:49 UTC |
| be87ce4 | Maikel van den Hurk | 25 February 2019, 07:28:47 UTC | Add ASM Compiler detection for QCC | 25 February 2019, 07:28:47 UTC |
| 47caf14 | Craig Scott | 24 February 2019, 09:05:49 UTC | Help: Add release note for new ARCH_INDEPENDENT option | 24 February 2019, 09:05:49 UTC |
| 4d55c1f | Craig Scott | 24 February 2019, 06:23:58 UTC | Help: Caveat for try_compile() and CMAKE_TRY_COMPILE_PLATFORM_VARIABLES | 24 February 2019, 06:23:58 UTC |
| 861dbef | Craig Scott | 24 February 2019, 06:22:53 UTC | Help: Consistency in try_compile() docs for target type | 24 February 2019, 06:22:53 UTC |
| df8aa3c | Craig Scott | 24 February 2019, 06:19:45 UTC | Help: try_compile() readability and grammar improvements | 24 February 2019, 06:19:45 UTC |
| 7975ede | Craig Scott | 24 February 2019, 06:13:45 UTC | Help: User-provided variable names for try_* commands All uppercase is typically used for command keywords. Non-keyword arguments should generally be shown as `<something>` according to the CMake documentation guide. | 24 February 2019, 06:16:07 UTC |
| 92d9ec9 | Craig Scott | 23 February 2019, 10:16:03 UTC | CheckLangSourceRuns: Capture run output to log files Fixes: #18973 | 23 February 2019, 10:16:03 UTC |
| 6ebe40c | Brad King | 22 February 2019, 16:19:09 UTC | Merge branch 'remove-exclude-from-all-warning' into release-3.14 Merge-request: !3002 | 22 February 2019, 16:19:09 UTC |
| d3b765d | Craig Scott | 21 February 2019, 12:00:50 UTC | EXCLUDE_FROM_ALL: Don't warn if installing target excluded from all The original warning pre-dates support for install components. There are now legitimate scenarios where an install(TARGETS) command may list a target that is excluded from all, e.g. hierarchical projects that will never install the component such a target belongs to. Fixes: #18938 | 21 February 2019, 20:55:56 UTC |
| c925166 | Brad King | 20 February 2019, 19:32:37 UTC | Merge branch 'link-options' into release-3.14 Merge-request: !2996 | 20 February 2019, 19:32:37 UTC |
