summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorCraig Scott <craig.scott@crascit.com>2019-01-22 10:35:39 (GMT)
committerBrad King <brad.king@kitware.com>2019-01-22 19:07:20 (GMT)
commit6b85eea3656e30aca7249ca4b903884d3bc73020 (patch)
treeae073991461d6ba1bbf1282b00696aab2c96044b
parent2395b1b244743aaf28426a72f37d1aac96e3db9e (diff)
downloadCMake-6b85eea3656e30aca7249ca4b903884d3bc73020.zip
CMake-6b85eea3656e30aca7249ca4b903884d3bc73020.tar.gz
CMake-6b85eea3656e30aca7249ca4b903884d3bc73020.tar.bz2
Help: Add 3.13.4 release note for no source/build dir error/warning
-rw-r--r--Help/release/3.13.rst26
1 files changed, 26 insertions, 0 deletions
diff --git a/Help/release/3.13.rst b/Help/release/3.13.rst
index 68e05c3..1c58550 100644
--- a/Help/release/3.13.rst
+++ b/Help/release/3.13.rst
@@ -252,3 +252,29 @@ Changes made since CMake 3.13.0 include the following.
directories to the ``moc`` tool for :prop_tgt:`AUTOMOC`. This has
been reverted due to regressing existing builds and will need
further investigation before being re-introduced in a later release.
+
+3.13.3
+------
+
+* The :generator:`Visual Studio 15 2017` generator has been fixed to work
+ when VS 2019 is installed.
+
+* CMake now checks that at least one of the source or binary directory
+ is specified when running CMake and issues an error if both are missing.
+ This has always been a documented requirement, but the implementation
+ previously accidentally accepted cases in which neither are specified
+ so long as some other argument is given, and silently used the current
+ working directory as the source and build tree.
+
+3.13.4
+------
+
+* The error added by 3.13.3 in cases that neither a source or binary
+ directory is specified has been downgraded to a warning. While this
+ was never intended, documented, nor supported behavior, some projects
+ relied on it. The error has been downgraded to a warning for the
+ remainder of the 3.13.x release series to allow a transition period,
+ but it may become a fatal error again in a later release. Scripts
+ relying on the old behavior can be trivially fixed by specifying
+ the path to the source tree (even if just ``.``) explicitly and
+ continue to work with all versions of CMake.