summaryrefslogtreecommitdiffstats
path: root/Help/release/3.14.rst
Commit message (Collapse)AuthorAgeFilesLines
* FindBISON: Fix CMP0088 NEW behavior for non-absolute input pathsBrian Carlson2019-07-121-0/+8
| | | | | | | | Now that the working directory is in the build tree, relative input paths must be converted to an absolute path to remain relative to the source directory. Fixes: #19472
* Do not exclude include directories made implicit by CPATHBrad King2019-05-301-0/+8
| | | | | | | | | | | | | | | | | | Entries of the `CPATH` environment variable are implicitly searched as include directories by some C/C++ compilers. Since commit 5990ecb741 (Compute implicit include directories from compiler output, 2018-12-07, v3.14.0-rc1~108^2) these entries are detected by CMake and included in the `CMAKE_{C,CXX}_IMPLICIT_INCLUDE_DIRECTORIES` variables. However, we should not exclude them from explicit specification via `-I` or particularly `-isystem` because they are meant as user-specified include directories that can be re-ordered without breaking compiler builtin headers. In particular, we need explicit requests via `include_directories` with the `SYSTEM` option to result in `-isystem` so that third-party headers do not produce warnings. Co-Author: Ben Boeckel <ben.boeckel@kitware.com> Fixes: #19291
* Help: Add 3.14.4 release notesBrad King2019-05-141-0/+10
| | | | | | Add a note about the fix in commit 3d3713121b (target_link_libraries: Fix static library private deps in other dirs, 2019-04-30). Also reference the equivalent note already added to the 3.13.5 notes.
* VS: Provide the default platform name to project codeBrad King2019-04-191-0/+11
| | | | | | | | | | | | | | | | | | The value of `CMAKE_VS_PLATFORM_NAME` is computed by Visual Studio generators based on `CMAKE_GENERATOR_PLATFORM` or some default. Prior to the VS 2019 generator, the default was always `Win32`. However, for the `Visual Studio 16 2019` generator, the default is based on the host platform. Store the default in a new `CMAKE_VS_PLATFORM_NAME_DEFAULT` variable for use by project code. This is particularly useful in toolchain files because they are allowed to set `CMAKE_GENERATOR_PLATFORM` and so `CMAKE_VS_PLATFORM_NAME` is not yet known. Of course the toolchain file author knows whether it will set `CMAKE_GENERATOR_PLATFORM`, and if not then `CMAKE_VS_PLATFORM_NAME_DEFAULT` provides the platform name that will be used. Fixes: #19177
* FindFontconfig: Convert module variables to camel caseBrad King2019-03-261-0/+14
| | | | | | | | | | | | | | | | 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
* Merge branch 'vs2019' into release-3.14Brad King2019-02-281-1/+1
|\ | | | | | | Merge-request: !3044
| * Help: Update VS 2019 generator release note for preview 4Brad King2019-02-281-1/+1
| |
* | Merge branch 'FindOctave-remove' into release-3.14Brad King2019-02-271-2/+0
|\ \ | | | | | | | | | Merge-request: !3027
| * | FindOctave: Remove module pending further workBrad King2019-02-261-2/+0
| |/ | | | | | | | | | | | | | | | | | | | | 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
* | Merge branch 'releasenotes_arch_independent' into release-3.14Brad King2019-02-251-0/+5
|\ \ | | | | | | | | | Merge-request: !3012
| * | Help: Add release note for new ARCH_INDEPENDENT optionCraig Scott2019-02-241-0/+5
| |/
* | Merge branch 'remove-exclude-from-all-warning' into release-3.14Brad King2019-02-221-0/+4
|\ \ | | | | | | | | | Merge-request: !3002
| * | EXCLUDE_FROM_ALL: Don't warn if installing target excluded from allCraig Scott2019-02-211-0/+4
| |/ | | | | | | | | | | | | | | | | 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
* | Release notes: Make ExternalProject dot points consistentCraig Scott2019-02-171-1/+1
|/ | | Use same phrasing and command linking.
* Merge branch 'ghs-relnotes' into release-3.14Brad King2019-02-111-0/+28
|\ | | | | | | Merge-request: !2934
| * Help: Update 3.14 release notes for GHS changesFred Baksik2019-02-111-0/+28
| |
* | Help: Add notes for `file(CREATE_LINK)` subcommandTushar Maheshwari2019-02-081-0/+3
|/
* Help: Clarify 3.14 release note about object library dependenciesBrad King2019-02-071-2/+2
| | | | | Revise the note from commit bab24e782c (target_link_libraries: Propagate dependencies of object libraries, 2018-12-10, v3.14.0-rc1~260^2).
* Help: Organize and revise 3.14 release notesBrad King2019-02-061-154/+200
| | | | | Add section headers similar to the 3.13 release notes and move each individual bullet into an appropriate section. Revise a few bullets.
* Help: Consolidate 3.14 release notesBrad King2019-02-061-0/+295
Run the `Utilities/Release/consolidate-relnotes.bash` script to move notes from `Help/release/dev/*` into `Help/release/3.14.rst`.