summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'vs-v142-csharp-flags' into release-3.16Brad King2019-10-112-2/+575
|\ | | | | | | Merge-request: !3908
| * VS: Add toolset v142 CSharp flag tableBrad King2019-10-112-2/+575
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Merge branch 'FindPostgreSQL-macports-and-v12' into release-3.16Brad King2019-10-111-1/+4
|\ \ | | | | | | | | | Merge-request: !3907
| * | FindPostgreSQL: support macports installation schemeBen Boeckel2019-10-111-0/+3
| | | | | | | | | | | | | | | | | | Macports installs into `include/postgresql${suffix}`. Add this to the list of supported suffixes. Also copy the non-server `postgresql/${suffix}` path.
| * | FindPostgreSQL: support version 12Ben Boeckel2019-10-111-1/+1
| | |
* | | Merge branch 'iar-8051-support' into release-3.16Brad King2019-10-116-3/+23
|\ \ \ | | | | | | | | | | | | Merge-request: !3906
| * | | IAR: Add 8051 supportMicael Borgefeldt2019-10-116-2/+22
| | | | | | | | | | | | | | | | Issue: #17264
| * | | IAR: Fix v850 assembler support file extensionsMicael Borgefeldt2019-10-111-1/+1
| |/ / | | | | | | | | | | | | | | | | | | Fix the file extension added by commit 158f3795b8 (IAR: Add v850 assembler support, 2019-09-23, v3.16.0-rc1~70^2). Issue: #17264
* | | Merge branch 'objc-c++flags' into release-3.16Brad King2019-10-114-1/+29
|\ \ \ | | | | | | | | | | | | Merge-request: !3904
| * | | Objective-C: Do not treat Objective-C files as C++ filesCristian Adam2019-10-114-1/+29
| |/ / | | | | | | | | | | | | When both C and C++ langauges are enabled, the Objective-C files should be treated as C files and not as C++ files.
* | | Merge branch 'doc-unity-build' into release-3.16Brad King2019-10-114-17/+37
|\ \ \ | | | | | | | | | | | | Merge-request: !3905
| * | | Help: Document CMAKE_UNITY_BUILD/CMAKE_EXPORT_COMPILE_COMMANDS limitationBrad King2019-10-113-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | These two options currently do not work well together. Mention this limitation in the documentation. Issue: #19826
| * | | Help: Extend documentation of CMAKE_UNITY_BUILD variableBrad King2019-10-111-3/+5
| | | |
| * | | Help: Improve UNITY_BUILD documentation formattingBrad King2019-10-111-15/+15
| | | |
| * | | Help: Document CMAKE_UNITY_BUILD in 3.16 release notesBrad King2019-10-111-0/+4
| |/ /
* | | Merge branch 'intel-19-compile-features' into release-3.16Brad King2019-10-113-4/+30
|\ \ \ | |/ / |/| | | | | Merge-request: !3900
| * | Tests: Update CompileFeatures test for Intel 19 with VS 2015Brad King2019-10-101-0/+6
| | | | | | | | | | | | | | | Blacklist `cxx_relaxed_constexpr` for this case because the compiler does not advertise the support in this mode but compiles our example.
| * | Intel: Fix default C++ dialect detection on WindowsBrad King2019-10-102-4/+24
|/ / | | | | | | | | | | For the Intel Compiler for Windows we have some subtle preprocessor checks in compiler feature detection to detect C++11 and C++14 modes. Use these when detecting the default C++ dialect too.
* | CMake 3.16.0-rc1v3.16.0-rc1Brad King2019-10-101-1/+1
| |
* | Merge branch 'rename_loglevel_option' into release-3.16Brad King2019-10-1020-44/+160
|\ \ | | | | | | | | | Merge-request: !3899
| * | CLI: Rename --loglevel to --log-level for naming consistencyCraig Scott2019-10-1020-44/+160
| | | | | | | | | | | | | | | | | | | | | Other multi-word command line options use hyphens to separate the words, so the --loglevel option introduced in CMake 3.15 was inconsistent in this regard. Rename it to --log-level but still support the original --loglevel name to preserve backward compatibility.
* | | Merge branch 'pch-generate' into release-3.16Brad King2019-10-1015-89/+255
|\ \ \ | | | | | | | | | | | | Merge-request: !3890
| * | | PCH: Generate sources during Compute stepCristian Adam2019-10-0915-89/+255
| | | |
* | | | Merge branch 'ExternalProject-minor-typos' into release-3.16Brad King2019-10-091-2/+2
|\ \ \ \ | | | | | | | | | | | | | | | Merge-request: !3898
| * | | | ExternalProject: fix some documentation typosBen Boeckel2019-10-091-2/+2
| | |/ / | |/| |
* | | | Merge branch 'vs-16.4-global-targets' into release-3.16Brad King2019-10-091-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 'file-GENERATE-earlier' into release-3.16Brad King2019-10-094-15/+11
|\ \ \ \ | | |/ / | |/| | | | | | Merge-request: !3895
| * | | file(GENERATE): Create output file structures even earlierBrad King2019-10-074-15/+11
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit b80557c7bd (file(GENERATE): Evaluate early to allow generating source files, 2014-11-04, v3.2.0-rc1~398^2) we create the `cmSourceFile` instances marked with a `GENERATED` source file property before tracing source dependencies. Move it to even earlier so that steps in `cmGlobalGenerator::AddAutomaticSources` can operate on all sources. This also avoids the accidental `O(n^2)` calls for `n` local generators that we had previously. This is also needed since commit 83c1657ff7 (Unity build: Generate sources during Compute step, 2019-10-03) to support `file(GENERATE)` outputs as sources in a target with `UNITY_BUILD` enabled.
* | | Merge branch 'apple-asm-deployment-target' into release-3.16Brad King2019-10-091-0/+2
|\ \ \ | | | | | | | | | | | | Merge-request: !3894
| * | | Apple: Set Clang ASM compiler featuresGregor Jasny2019-10-091-0/+2
| |/ / | | | | | | | | | | | | | | | | | | | | | The same is done for the C and CXX language. This initializes compiler flags like the sysroot path or deployment target. Closes: #19794 Suggested-by: Kyle Fleming
* | | Begin 3.16 release versioningBrad King2019-10-071-3/+3
| | |
* | | Help: Drop development topic notes to prepare releaseBrad King2019-10-072-9/+0
|/ / | | | | | | | | Release versions do not have the development topic section of the CMake Release Notes index page.
* | Merge topic 'doc-3.16-relnotes'Brad King2019-10-0744-295/+271
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | ffa1c76ba3 Help: Add missing 3.16 release notes for CPack/DEB descriptions a933d8d84e Help: Organize and revise 3.16 release notes 9c9a6e6023 Help: Consolidate 3.16 release notes Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3889
| * | Help: Add missing 3.16 release notes for CPack/DEB descriptionsBrad King2019-10-071-0/+8
| | | | | | | | | | | | | | | | | | | | | Add notes for the changes from commit 33c7ea513d (CPackDeb: Use `CPACK_PACKAGE_DESCRIPTION_FILE`, 2019-07-11). Suggested-by: Alex Turbov <i.zaufi@gmail.com>
| * | Help: Organize and revise 3.16 release notesBrad King2019-10-071-135/+178
| | | | | | | | | | | | | | | | | | Add section headers similar to the 3.15 release notes and move each individual bullet into an appropriate section. Revise a few bullets. Drop bullets covering internal interfaces.
| * | Help: Consolidate 3.16 release notesBrad King2019-10-0444-295/+220
| | | | | | | | | | | | | | | Run the `Utilities/Release/consolidate-relnotes.bash` script to move notes from `Help/release/dev/*` into `Help/release/3.16.rst`.
* | | Merge topic 'doc_custom_commands_crosscompile'Brad King2019-10-072-25/+45
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | c6f08a2125 Help: Clarify how target names are handled in custom commands/targets Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3891
| * | | Help: Clarify how target names are handled in custom commands/targetsCraig Scott2019-10-052-25/+45
| | | | | | | | | | | | Fixes: #19771
* | | | Merge topic 'export-genex-under-prefix'Brad King2019-10-072-4/+7
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3ded5b6da8 install,export: Fix export of a genex following $<INSTALL_PREFIX> Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3886
| * | | | install,export: Fix export of a genex following $<INSTALL_PREFIX>Brad King2019-10-042-4/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The relative path check added by commit 5838aba1aa (Export: Report error on relative include with genex., 2013-11-26, v3.0.0-rc1~285^2) was added one condition too early. If the value starts in `${_IMPORT_PREFIX}` (which comes from `$<INSTALL_PREFIX>`) then it is an absolute path. Fixes: #19791
* | | | | Merge topic 'test-per-config-sources'Brad King2019-10-079-23/+71
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 9c9e66289a Tests: Enable ConfigSources test on every configuration Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3888
| * | | | | Tests: Enable ConfigSources test on every configurationBrad King2019-10-049-23/+71
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | Revise the test itself to work in all configurations and verify that certain sources are only built by whatever configuration is tested.
* | | | | Merge topic 'doc-install-strip'Brad King2019-10-072-6/+36
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 12368e6d15 Help: Document install/strip targets for Ninja/UNIX Makefiles generators Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3887
| * | | | | Help: Document install/strip targets for Ninja/UNIX Makefiles generatorsCristian Adam2019-10-042-6/+36
| | |/ / / | |/| | |
* | | | | CMake Nightly Date StampKitware Robot2019-10-071-1/+1
| | | | |
* | | | | CMake Nightly Date StampKitware Robot2019-10-061-1/+1
| |_|/ / |/| | |
* | | | CMake Nightly Date StampKitware Robot2019-10-051-1/+1
| |/ / |/| |
* | | Merge topic 'unity-step'Brad King2019-10-0411-10/+28
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 83c1657ff7 Unity build: Generate sources during Compute step Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !3884
| * | | Unity build: Generate sources during Compute stepBrad King2019-10-0311-10/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The unity build sources need to be added for all generators. Create them during `cmGlobalGenerator::Compute` to avoid duplicating the calls in every generator. We already handle Qt autogen there too. Issue: #19789
generated by cgit v0.12 at 2025-08-26 11:30:25 (GMT)