summaryrefslogtreecommitdiffstats
path: root/Source
Commit message (Collapse)AuthorAgeFilesLines
* Makefiles: Fix silencing of nested calls for GNU make 4.3Brad King2020-03-261-1/+5
| | | | | | | | Since GNU make 4.3, `.SILENT:` no longer causes nested `$(MAKE)` calls to get `-s` implicitly. Add the `-s` flag explicitly on such calls to suppress messages about Entering/Leaving directories. Fixes: #20487
* CMake 3.16.5v3.16.5Brad King2020-03-041-1/+1
|
* Merge branch 'backport-cuda-non-device-link' into release-3.16Brad King2020-02-241-2/+2
|\ | | | | | | Merge-request: !4376
| * Ninja: Do not use nvcc response files with non-nvcc toolsFrancisco Facioni2020-02-241-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | Since commit d91b5a72cd (Ninja: Add support for CUDA nvcc response files, 2019-05-30, v3.15.0-rc1~8^2) we use NVCC's `--options-file` option to avoid long link command lines via a response file. However, for non-device linking the host tools are used and the option does not make sense. Update the logic to use `--options-file` only for device linking. Linking with the host tools already has its own logic for response files. Fixes: #19954
| * CMake 3.15.7v3.15.7Brad King2020-02-041-1/+1
| |
| * Merge branch 'vs-16.4-custom-command-inputs' into release-3.15Brad King2020-01-281-1/+7
| |\ | | | | | | | | | Merge-request: !4297
* | \ Merge branch 'backport-3.16-install-default-fix' into release-3.16Brad King2020-02-121-6/+38
|\ \ \
| * | | install: Fix regression when using default destinationsKyle Edwards2020-02-111-6/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit 9fc20a4f3e (install: Add sane set of defaults for DESTINATION and file type parameters, 2018-11-02, v3.14.0-rc1~410^2~1), a regression was introduced, in which an `install(TARGETS)` with a RUNTIME/LIBRARY/ARCHIVE DESTINATION but no PUBLIC_HEADER/PRIVATE_HEADER DESTINATION would then install the headers. The old behavior did not do this. Restore the old behavior. Fixes: #20326
* | | | Propagate backtraces from LINK_LIBRARIES through to link line itemsBrad King2020-02-109-93/+85
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit d4d0dd0f6a (cmLinkLineComputer: Add ComputeLinkLibs overload with backtraces, 2019-09-13, v3.16.0-rc1~87^2~4), backtraces have been collected by `ComputeLinkLibs` by looking back through the link implementation libraries for one matching the text of the link line item. This is slow in projects with long link lines. Instead, teach `cmComputeLinkDepends` and `cmComputeLinkInformation` to carry backtrace information explicitly along with the text of each item. Fixes: #20322
* | | CMake 3.16.4v3.16.4Brad King2020-02-051-1/+1
| | |
* | | Merge topic 'vs-version-for-unity' into release-3.16Brad King2020-02-053-7/+12
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 9135954e2f VS: Do not use native unity builds on VS 2017 versions less than 15.8 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4324
| * | | VS: Do not use native unity builds on VS 2017 versions less than 15.8Brad King2020-02-043-7/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | VS 2017 version 15.8 introduced support for unity builds implemented in part by the `$(VCTargetsPath)/Microsoft.Cpp.Unity.targets` file. Do not enable unity builds on VS 15 versions that do not have that file. Fixes: #20284
* | | | Merge topic 'vs-16.4-custom-command-inputs' into release-3.16Brad King2020-01-291-1/+7
|\ \ \ \ | | |_|/ | |/| | | | | | | | | | | | | | | | | | 58b0674687 VS: Tell VS 16.4 not to verify SYMBOLIC custom command inputs Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4297
| * | | VS: Tell VS 16.4 not to verify SYMBOLIC custom command inputsBrad King2020-01-281-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 SYMBOLIC *inputs* too. This is needed when there is a chain of custom commands that use symbolic paths for ordering. Fixes: #20179
* | | | file(GET_RUNTIME_DEPENDENCIES): Tolerate empty list argumentsKyle Edwards2020-01-221-3/+14
| |/ / |/| | | | | | | | | | | Also list all keywords that were missing values instead of only the first one.
* | | CMake 3.16.3v3.16.3Brad King2020-01-211-1/+1
| | |
* | | Merge topic 'autogen_rcc_skip_unity' into release-3.16Brad King2020-01-202-14/+19
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 086d9b2bab Autogen: Enable SKIP_UNITY_BUILD_INCLUSION on AUTORCC generated files Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Cristian Adam <cristian.adam@gmail.com> Merge-request: !4237
| * | | Autogen: Enable SKIP_UNITY_BUILD_INCLUSION on AUTORCC generated filesSebastian Holtermann2020-01-172-14/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `rcc` generated files are not compatible with unity builds, because they contain classes in anonymous namespaces and static data with identical names. This patch sets the source file property `SKIP_UNITY_BUILD_INCLUSION` to `On` on all `AUTORCC` generated files to exclude them from unity build files. Fixes: #20191 "QT5: Exclude resource files from unity build"
* | | | Merge topic 'pch-msvc-no-path-repetition' into release-3.16Craig Scott2020-01-191-1/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 07fe1bcd4e PCH: No repeated path for internal generated PCH files (MSVC case) Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4236
| * | | | PCH: No repeated path for internal generated PCH files (MSVC case)Cristian Adam2020-01-161-1/+2
| | | | | | | | | | | | | | | | | | | | Fixes: #19952
* | | | | Merge topic 'nag-submodule' into release-3.16Brad King2020-01-161-2/+6
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | f7f60ddcf9 Fortran: Add support for NAG Fortran submodules Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4229
| * | | | Fortran: Add support for NAG Fortran submodulesNeil Carlson2020-01-151-2/+6
| |/ / / | | | | | | | | | | | | | | | | | | | | They use a `.sub` extension. Fixes: #20220
* | | | Unity Build: include language in generated source file nameCristian Adam2020-01-141-1/+1
| | | | | | | | | | | | | | | | Fixes: #20206
* | | | Merge topic 'vs-Fortran-link-flags' into release-3.16Brad King2020-01-141-0/+8
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | a3c827b2ea VS: Add Fortran link flag table entries for /OPT:* Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4210
| * | | | VS: Add Fortran link flag table entries for /OPT:*Pavel Liavonau2020-01-131-0/+8
| |/ / / | | | | | | | | | | | | Fixes: #20190
* | | | Merge topic 'fix-cpack-deb-description-file' into release-3.16Brad King2020-01-131-2/+7
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | d491f34a5e CPack: Fix regression in DEB generator description Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4204
| * | | | CPack: Fix regression in DEB generator descriptionKyle Edwards2020-01-101-2/+7
| | | | | | | | | | | | | | | | | | | | Fixes: #20102
* | | | | Merge topic 'objc-visibility-inlines' into release-3.16Brad King2020-01-131-4/+5
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | 7347e2f830 ObjC: Add VISIBLITY_INLINES_HIDDEN support Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4199
| * | | | ObjC: Add VISIBLITY_INLINES_HIDDEN supportCristian Adam2020-01-101-4/+5
| | | | | | | | | | | | | | | | | | | | Fixes: #20193
* | | | | Merge topic 'cuda-device-link-only-cuda' into release-3.16Brad King2020-01-101-17/+17
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7ffa42288e Merge branch 'backport-3.15-cuda-device-link-only-cuda' 071c4f1a2a CUDA: Do not device link if target has no CUDA usage Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4191
| * \ \ \ \ Merge branch 'backport-3.15-cuda-device-link-only-cuda'Brad King2020-01-091-17/+17
| |\ \ \ \ \ | | |/ / / / | |/| | | / | | | |_|/ | | |/| |
| | * | | CUDA: Do not device link if target has no CUDA usageRobert Maynard2020-01-091-18/+18
| | | |/ | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When CUDA is enabled, and a pure non-CUDA target has CMAKE_CUDA_SEPARABLE_COMPILATION enabled, don't actually perform the device linking step, as it will fail. A target that has CMAKE_CUDA_SEPARABLE_COMPILATION enabled must also have CUDA usage (either itself, or something it links to). Fixes: #20182
| | * | CMake 3.15.6v3.15.6Brad King2019-12-161-1/+1
| | | |
| | * | Merge branch 'backport-3.15-vs-v142-version' into release-3.15Brad King2019-12-121-9/+11
| | |\ \ | | | | | | | | | | | | | | | Merge-request: !4133
| | | * | VS: Fix support for v142 toolset minor versions in VS 16.5+Brad King2019-12-121-9/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The fix in commit 5117389931 (VS: Fix support for v142 toolset minor versions, 2019-10-01, v3.15.5~6^2) worked around a bug in VS's placement of toolset files. VS 16.5 will fix that bug and restore the original pattern for locations of toolset files. Update our logic to look for both possibilities. Issue: #19779
| | * | | Check for support before adding bigtoc linker flagAlexander Grund2019-12-091-0/+25
| | |/ / | | | | | | | | | | | | Fixes: #20076
| | * | CMake 3.15.5v3.15.5Brad King2019-10-301-1/+1
| | | |
| | * | Merge branch 'vs-v142-csharp-flags' into release-3.15Brad King2019-10-111-2/+1
| | |\ \ | | | | | | | | | | | | | | | Merge-request: !3908
| | * \ \ Merge branch 'backport-vs-16.4-global-targets' into release-3.15Brad King2019-10-071-0/+4
| | |\ \ \ | | | | | | | | | | | | | | | | | | Merge-request: !3896
| | | * | | VS: Tell VS 16.4 not to verify CMake-provided custom command outputsBrad King2019-10-071-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| | * | | | Merge branch 'backport-xcode-scheme-custom-target' into release-3.15Brad King2019-10-021-1/+6
| | |\ \ \ \ | | | | | | | | | | | | | | | | | | | | | Merge-request: !3878
| | | * | | | Xcode: Restore CMAKE_XCODE_GENERATE_SCHEME for custom targetsBrad King2019-10-021-1/+6
| | | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | | | ObjC: Add _COMPILE_LAUNCHER supportCristian Adam2020-01-093-3/+6
|/ / / / / | | | | | | | | | | | | | | | Fixes: #20178
* | | | | CTest: Improve error handling when reading resource spec fileKyle Edwards2019-12-273-23/+81
| |_|_|/ |/| | | | | | | | | | | Fixes: #20079
* | | | CMake 3.16.2v3.16.2Brad King2019-12-191-1/+1
| | | |
* | | | Merge topic 'autogen-no-hh' into release-3.16Brad King2019-12-191-2/+4
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7fa7f55230 Autogen: Revert processing of .hh files for compatibility Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4146
| * | | | Autogen: Revert processing of .hh files for compatibilityBrad King2019-12-181-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit 4a9154537c (Autogen: Use cmake::IsHeader/SourceExtension for file type detection, 2019-07-02, v3.16.0-rc1~470^2~4) we process `.hh` files with `AUTOMOC`. However, this change can break existing projects that do not expect the behavior. Revert it for now. It can be restored later via a policy. Fixes: #20101
* | | | | Merge topic 'pch-force-include' into release-3.16Brad King2019-12-161-0/+3
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | c5c218fa0d PCH: Append pch header file to list of forced include files Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4135
| * | | | | PCH: Append pch header file to list of forced include filesCristian Adam2019-12-131-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | Fixes: #20088
* | | | | | VS: Fix support for v142 toolset minor versions in VS 16.5+Brad King2019-12-121-9/+14
| |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The fix in commit 5117389931 (VS: Fix support for v142 toolset minor versions, 2019-10-01, v3.16.0-rc1~32^2) worked around a bug in VS's placement of toolset files. VS 16.5 will fix that bug and restore the original pattern for locations of toolset files. Update our logic to look for both possibilities. Issue: #19779
generated by cgit v0.12 at 2024-11-07 10:07:33 (GMT)