Help: Consolidate 3.2 release notes
Move all development release notes into a new version-specific document: tail -q -n +3 Help/release/dev/* > Help/release/3.2.0.rst git rm -- Help/release/dev/* except the sample topic: git checkout HEAD -- Help/release/dev/0-sample-topic.rst Reference the new document from the release notes index document. Add a title and intro sentence to the new document by hand.
This commit is contained in:
Brad King
parent
3a4381b660
commit
e08a78dc2c
|
|
@ -0,0 +1,249 @@
|
|||
CMake 3.2.0 Release Notes
|
||||
*************************
|
||||
|
||||
.. only:: html
|
||||
|
||||
.. contents::
|
||||
|
||||
Changes made since CMake 3.1.0 include the following.
|
||||
|
||||
* A new :command:`continue` command was added that can be called inside loop
|
||||
contexts to end the current iteration and start the next one at the top of
|
||||
the loop block.
|
||||
|
||||
* A :module:`FindGSL` module was introduced to find the
|
||||
GNU Scientific Library.
|
||||
|
||||
* The :module:`FindIntl` module was added to find the Gettext ``libintl``
|
||||
library.
|
||||
|
||||
* A :module:`FindJsonCpp` module was introduced to find the
|
||||
JsonCpp package.
|
||||
|
||||
* The :command:`ctest_coverage` learned to support Javascript coverage.
|
||||
|
||||
* The :manual:`cmake(1)` ``-E tar`` command now supports creating
|
||||
``.xz``-compressed archives with the ``J`` flag.
|
||||
|
||||
* On OS X with Makefile and Ninja generators, when a compiler is found
|
||||
in ``/usr/bin`` it is now mapped to the corresponding compiler inside
|
||||
the Xcode application folder, if any. This allows such build
|
||||
trees to continue to work with their original compiler even when
|
||||
``xcode-select`` switches to a different Xcode installation.
|
||||
|
||||
* The :manual:`Compile Features <cmake-compile-features(7)>` functionality
|
||||
is now aware of features supported by GNU compilers on OS X.
|
||||
|
||||
* The :command:`break` command now rejects calls outside of a loop
|
||||
context or that pass arguments to the command.
|
||||
See policy :policy:`CMP0055`.
|
||||
|
||||
* Add :variable:`CMAKE_MATCH_COUNT` for the number of matches made in the last
|
||||
regular expression.
|
||||
|
||||
* The :manual:`cmake(1)` ``-E tar`` command learned a new
|
||||
``--files-from=<file>`` option to specify file names using
|
||||
lines in a file to overcome command-line length limits.
|
||||
|
||||
* The :manual:`cmake(1)` ``-E tar`` command learned a new
|
||||
``--mtime=<date>`` option to specify the modification time
|
||||
recorded in tarball entries.
|
||||
|
||||
* The :command:`add_custom_command` and :command:`add_custom_target`
|
||||
commands learned a new ``USES_TERMINAL`` option to request that
|
||||
the command be given direct access to the terminal if possible.
|
||||
The :generator:`Ninja` generator will places such commands in the
|
||||
``console`` pool. Build targets provided by CMake that are meant
|
||||
for individual interactive use, such as ``install``, are now
|
||||
placed in this pool.
|
||||
|
||||
* The :module:`CPackRPM` module learned options to set per-component
|
||||
descriptions and summaries. See the
|
||||
:variable:`CPACK_RPM_<component>_PACKAGE_DESCRIPTION` and
|
||||
:variable:`CPACK_RPM_<component>_PACKAGE_SUMMARY` variables.
|
||||
|
||||
* The :module:`CPackRPM` module learned options to specify
|
||||
requirements for pre- and post-install scripts. See the
|
||||
:variable:`CPACK_RPM_PACKAGE_REQUIRES_PRE` and
|
||||
:variable:`CPACK_RPM_PACKAGE_REQUIRES_POST` variables.
|
||||
|
||||
* The :module:`CPackRPM` module learned options to specify
|
||||
requirements for pre- and post-uninstall scripts. See the
|
||||
:variable:`CPACK_RPM_PACKAGE_REQUIRES_PREUN` and
|
||||
:variable:`CPACK_RPM_PACKAGE_REQUIRES_POSTUN` variables.
|
||||
|
||||
* The :module:`CTestCoverageCollectGCOV` module was introduced as an
|
||||
alternative to the :command:`ctest_coverage` command for collecting
|
||||
``gcov`` results for submission to CDash.
|
||||
|
||||
* The :command:`ctest_coverage` learned to support Delphi coverage.
|
||||
|
||||
* On OS X, commands supporting network communication, such as
|
||||
:command:`file(DOWNLOAD)`, :command:`file(UPLOAD)`, and
|
||||
:command:`ctest_submit`, now support SSL/TLS even when CMake
|
||||
is not built against OpenSSL. The OS X native SSL/TLS
|
||||
implementation is used by default. OS-configured certificate
|
||||
authorities will be trusted automatically.
|
||||
|
||||
* When CMake is built with OpenSSL on systems other than Windows
|
||||
and OS X, commands supporting network communication via ``https``,
|
||||
such as :command:`file(DOWNLOAD)`, :command:`file(UPLOAD)`, and
|
||||
:command:`ctest_submit`, now search for OS-configured certificate
|
||||
authorities in a few ``/etc`` paths to be trusted automatically.
|
||||
|
||||
* On Windows, commands supporting network communication, such as
|
||||
:command:`file(DOWNLOAD)`, :command:`file(UPLOAD)`, and
|
||||
:command:`ctest_submit`, now support SSL/TLS even when CMake
|
||||
is not built against OpenSSL. The Windows native SSL/TLS
|
||||
implementation is used by default. OS-configured certificate
|
||||
authorities will be trusted automatically.
|
||||
|
||||
* The :command:`add_custom_command` and :command:`add_custom_target`
|
||||
commands learned a new ``BYPRODUCTS`` option to specify files
|
||||
produced as side effects of the custom commands. These are not
|
||||
outputs because they do not always have to be newer than inputs.
|
||||
|
||||
* The :module:`ExternalData` module learned to support
|
||||
:ref:`Custom Fetch Scripts <ExternalData Custom Fetch Scripts>`.
|
||||
This allows projects to specify custom ``.cmake`` scripts for
|
||||
fetching data objects during the build.
|
||||
|
||||
* The :module:`ExternalProject` module ``ExternalProject_Add`` function
|
||||
learned a new ``CMAKE_CACHE_DEFAULT_ARGS`` option to initialize cache
|
||||
values in the external project without setting them on future builds.
|
||||
|
||||
* The :module:`ExternalProject` module learned options to create
|
||||
independent external project step targets that do not depend
|
||||
on the builtin steps.
|
||||
|
||||
* The :module:`ExternalProject` module :command:`ExternalProject_Add`
|
||||
command learned a ``TEST_EXCLUDE_FROM_MAIN`` option to exclude tests
|
||||
from the main build.
|
||||
|
||||
* The :module:`ExternalProject` module ``ExternalProject_Add`` command
|
||||
learned an ``UPDATE_DISCONNECTED`` option to avoid automatically
|
||||
updating the source tree checkout from version control.
|
||||
|
||||
* The :manual:`Compile Features <cmake-compile-features(7)>` functionality
|
||||
is now aware of features supported by Microsoft Visual Studio (``MSVC``).
|
||||
|
||||
* The :command:`file(LOCK)` subcommand was created to allow CMake
|
||||
processes to synchronize through file and directory locks.
|
||||
|
||||
* The :command:`file(STRINGS)` now supports UTF-16LE, UTF-16BE,
|
||||
UTF-32LE, UTF-32BE as ``ENCODING`` options.
|
||||
|
||||
* The :module:`FindCUDA` module learned about the ``cusolver``
|
||||
library in CUDA 7.0.
|
||||
|
||||
* The :module:`FindGit` module learned to find the ``git`` command-line tool
|
||||
that comes with GitHub for Windows installed in user home directories.
|
||||
|
||||
* The :module:`FindLATEX` module learned to support components.
|
||||
|
||||
* The :module:`FindMPI` module learned to find MS-MPI on Windows.
|
||||
|
||||
* The :module:`FindOpenGL` module no longer explicitly searches
|
||||
for any dependency on X11 libraries with the :module:`FindX11`
|
||||
module. Such dependencies should not need to be explicit.
|
||||
Applications using X11 APIs themselves should find and link
|
||||
to X11 libraries explicitly.
|
||||
|
||||
* The :module:`FindOpenSSL` module now reports ``crypto`` and ``ssl``
|
||||
libraries separately in ``OPENSSL_CRYPTO_LIBRARY`` and
|
||||
``OPENSSL_SSL_LIBRARY``, respectively, to allow applications to
|
||||
link to one without the other.
|
||||
|
||||
* The :manual:`Compile Features <cmake-compile-features(7)>` functionality
|
||||
is now aware of features supported by GNU 4.4 to 4.6 compilers.
|
||||
|
||||
* The :command:`install(EXPORT)` command now works with an absolute
|
||||
``DESTINATION`` even if targets in the export set are installed
|
||||
with a destination or usage requirements specified relative to the
|
||||
install prefix. The value of the :variable:`CMAKE_INSTALL_PREFIX`
|
||||
variable is hard-coded into the installed export file as the base
|
||||
for relative references.
|
||||
|
||||
* The :manual:`Compile Features <cmake-compile-features(7)>` functionality
|
||||
is now aware of features supported by GNU compiler version 5.0.
|
||||
|
||||
* The :module:`CPackRPM` module learned a new
|
||||
:variable:`CPACK_RPM_<COMPONENT>_PACKAGE_PREFIX` variable to
|
||||
specify a component-specific value to use instead of
|
||||
:variable:`CPACK_PACKAGING_INSTALL_PREFIX`.
|
||||
|
||||
* The :module:`CPackRPM` module learned a new
|
||||
:variable:`CPACK_RPM_RELOCATION_PATHS` variable to
|
||||
specify multiple relocation prefixes for a single rpm package.
|
||||
|
||||
* The :manual:`Compile Features <cmake-compile-features(7)>` functionality
|
||||
is now aware of features supported by Oracle SolarisStudio (``SunPro``).
|
||||
|
||||
* The :command:`try_compile` command source file signature now honors
|
||||
link flags (e.g. :variable:`CMAKE_EXE_LINKER_FLAGS`) in the generated
|
||||
test project. See policy :policy:`CMP0056`.
|
||||
|
||||
* The :command:`try_run` command learned to honor the ``LINK_LIBRARIES``
|
||||
option just as :command:`try_compile` already does.
|
||||
|
||||
* The implementation of CMake relies on some C++ compiler features which are
|
||||
not supported by some older compilers. As a result, those old compilers
|
||||
can no longer be used to build CMake itself. CMake continues to be able to
|
||||
generate Makefiles and project files for users of those old compilers
|
||||
however. The compilers known to no longer be capable of building CMake
|
||||
are:
|
||||
|
||||
* MSVC 6 and 7.0 - superceded by VisualStudio 7.1 and newer compilers.
|
||||
* GCC 2.95 - superceded by GCC 3 and newer compilers.
|
||||
* Borland compilers - superceded by other Windows compilers.
|
||||
* Compaq compilers - superceded by other compilers.
|
||||
* Comeau compilers - superceded by other compilers.
|
||||
* SGI compilers - IRIX was dropped as a host platform.
|
||||
|
||||
When building using SolarisStudio 12, the default ``libCStd`` standard
|
||||
library is not sufficient to build CMake. The SolarisStudio distribution
|
||||
supports compiler options to use ``STLPort4`` or ``libstdc++``. An
|
||||
appropriate option to select the standard library is now added
|
||||
automatically when building CMake with SolarisStudio compilers.
|
||||
|
||||
* A :prop_tgt:`ANDROID_API_MIN` target property was introduced to
|
||||
specify the minimum version to be targeted by the toolchain.
|
||||
|
||||
* A :prop_sf:`VS_SHADER_FLAGS` source file property was added to specify
|
||||
additional shader flags to ``.hlsl`` files, for the Visual Studio generators.
|
||||
|
||||
* The :module:`WriteCompilerDetectionHeader` module learned to
|
||||
create a define for portability of the cxx_thread_local feature. The define
|
||||
expands to either the C++11 ``thread_local`` keyword, or a
|
||||
pre-standardization compiler-specific equivalent, as appropriate.
|
||||
|
||||
* On Windows, CMake learned to support international characters.
|
||||
This allows use of characters from multiple (spoken) languages
|
||||
in CMake code, paths to source files, configured files such as
|
||||
``.h.in`` files, and other files read and written by CMake.
|
||||
Because CMake interoperates with many other tools, there may
|
||||
still be some limitations when using certain international
|
||||
characters.
|
||||
|
||||
Files written in the :manual:`cmake-language(7)`, such as
|
||||
``CMakeLists.txt`` or ``*.cmake`` files, are expected to be
|
||||
encoded as UTF-8. If files are already ASCII, they will be
|
||||
compatible. If files were in a different encoding, including
|
||||
Latin 1, they will need to be converted.
|
||||
|
||||
The Visual Studio generators now write solution and project
|
||||
files in UTF-8 instead of Windows-1252. Windows-1252 supported
|
||||
Latin 1 languages such as those found in North and South America
|
||||
and Western Europe. With UTF-8, additional languages are now
|
||||
supported.
|
||||
|
||||
* The :module:`WriteCompilerDetectionHeader` module learned to create
|
||||
multiple output files per compiler and per language, instead of creating
|
||||
one large file.
|
||||
|
||||
* The :manual:`Compile Features <cmake-compile-features(7)>` functionality
|
||||
is now aware of features supported by Apple Clang (``AppleClang``).
|
||||
|
||||
* The :generator:`Xcode` generator no longer requires a value for
|
||||
the :variable:`CMAKE_MAKE_PROGRAM` variable to be located up front.
|
||||
It now locates ``xcodebuild`` when needed at build time.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Apple-GNU-compiler-features
|
||||
---------------------------
|
||||
|
||||
* The :manual:`Compile Features <cmake-compile-features(7)>` functionality
|
||||
is now aware of features supported by GNU compilers on OS X.
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
Apple-compiler-selection
|
||||
------------------------
|
||||
|
||||
* On OS X with Makefile and Ninja generators, when a compiler is found
|
||||
in ``/usr/bin`` it is now mapped to the corresponding compiler inside
|
||||
the Xcode application folder, if any. This allows such build
|
||||
trees to continue to work with their original compiler even when
|
||||
``xcode-select`` switches to a different Xcode installation.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
CTestCoverageCollectGCOV-refinements
|
||||
------------------------------------
|
||||
|
||||
* The :module:`CTestCoverageCollectGCOV` module was introduced as an
|
||||
alternative to the :command:`ctest_coverage` command for collecting
|
||||
``gcov`` results for submission to CDash.
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
ExternalData-custom-download
|
||||
----------------------------
|
||||
|
||||
* The :module:`ExternalData` module learned to support
|
||||
:ref:`Custom Fetch Scripts <ExternalData Custom Fetch Scripts>`.
|
||||
This allows projects to specify custom ``.cmake`` scripts for
|
||||
fetching data objects during the build.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
ExternalProject_CMAKE_CACHE_DEFAULT_ARGS
|
||||
----------------------------------------
|
||||
|
||||
* The :module:`ExternalProject` module ``ExternalProject_Add`` function
|
||||
learned a new ``CMAKE_CACHE_DEFAULT_ARGS`` option to initialize cache
|
||||
values in the external project without setting them on future builds.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
ExternalProject_TEST_EXCLUDE_FROM_MAIN
|
||||
--------------------------------------
|
||||
|
||||
* The :module:`ExternalProject` module :command:`ExternalProject_Add`
|
||||
command learned a ``TEST_EXCLUDE_FROM_MAIN`` option to exclude tests
|
||||
from the main build.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
ExternalProject_UPDATE_DISCONNECTED
|
||||
-----------------------------------
|
||||
|
||||
* The :module:`ExternalProject` module ``ExternalProject_Add`` command
|
||||
learned an ``UPDATE_DISCONNECTED`` option to avoid automatically
|
||||
updating the source tree checkout from version control.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
ExternalProject_independent-step-targets
|
||||
----------------------------------------
|
||||
|
||||
* The :module:`ExternalProject` module learned options to create
|
||||
independent external project step targets that do not depend
|
||||
on the builtin steps.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
FindCUDA-cusolver
|
||||
-----------------
|
||||
|
||||
* The :module:`FindCUDA` module learned about the ``cusolver``
|
||||
library in CUDA 7.0.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
FindGit-local-Github
|
||||
--------------------
|
||||
|
||||
* The :module:`FindGit` module learned to find the ``git`` command-line tool
|
||||
that comes with GitHub for Windows installed in user home directories.
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
FindLATEX-components
|
||||
--------------------
|
||||
|
||||
* The :module:`FindLATEX` module learned to support components.
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
FindOpenGL-no-X11
|
||||
-----------------
|
||||
|
||||
* The :module:`FindOpenGL` module no longer explicitly searches
|
||||
for any dependency on X11 libraries with the :module:`FindX11`
|
||||
module. Such dependencies should not need to be explicit.
|
||||
Applications using X11 APIs themselves should find and link
|
||||
to X11 libraries explicitly.
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
FindOpenSSL-separate-libs
|
||||
-------------------------
|
||||
|
||||
* The :module:`FindOpenSSL` module now reports ``crypto`` and ``ssl``
|
||||
libraries separately in ``OPENSSL_CRYPTO_LIBRARY`` and
|
||||
``OPENSSL_SSL_LIBRARY``, respectively, to allow applications to
|
||||
link to one without the other.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
GNU-4.4-compile-features
|
||||
------------------------
|
||||
|
||||
* The :manual:`Compile Features <cmake-compile-features(7)>` functionality
|
||||
is now aware of features supported by GNU 4.4 to 4.6 compilers.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
SolarisStudio-compile-features
|
||||
------------------------------
|
||||
|
||||
* The :manual:`Compile Features <cmake-compile-features(7)>` functionality
|
||||
is now aware of features supported by Oracle SolarisStudio (``SunPro``).
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
WriteCompilerDetectionHeader thread_local portability
|
||||
-----------------------------------------------------
|
||||
|
||||
* The :module:`WriteCompilerDetectionHeader` module learned to
|
||||
create a define for portability of the cxx_thread_local feature. The define
|
||||
expands to either the C++11 ``thread_local`` keyword, or a
|
||||
pre-standardization compiler-specific equivalent, as appropriate.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
WriteCompilerDetectionHeader-multi-file
|
||||
---------------------------------------
|
||||
|
||||
* The :module:`WriteCompilerDetectionHeader` module learned to create
|
||||
multiple output files per compiler and per language, instead of creating
|
||||
one large file.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Xcode-clang-compile-features
|
||||
----------------------------
|
||||
|
||||
* The :manual:`Compile Features <cmake-compile-features(7)>` functionality
|
||||
is now aware of features supported by Apple Clang (``AppleClang``).
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
add-FindGSL
|
||||
-----------
|
||||
|
||||
* A :module:`FindGSL` module was introduced to find the
|
||||
GNU Scientific Library.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
add-FindIntl
|
||||
------------
|
||||
|
||||
* The :module:`FindIntl` module was added to find the Gettext ``libintl``
|
||||
library.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
add-FindJsonCpp
|
||||
---------------
|
||||
|
||||
* A :module:`FindJsonCpp` module was introduced to find the
|
||||
JsonCpp package.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
add-continue-command
|
||||
--------------------
|
||||
|
||||
* A new :command:`continue` command was added that can be called inside loop
|
||||
contexts to end the current iteration and start the next one at the top of
|
||||
the loop block.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
add-xz-support
|
||||
--------------
|
||||
|
||||
* The :manual:`cmake(1)` ``-E tar`` command now supports creating
|
||||
``.xz``-compressed archives with the ``J`` flag.
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
add_javascript_coverage_parser
|
||||
------------------------------
|
||||
|
||||
* The :command:`ctest_coverage` learned to support Javascript coverage.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
break-command-strictness
|
||||
------------------------
|
||||
|
||||
* The :command:`break` command now rejects calls outside of a loop
|
||||
context or that pass arguments to the command.
|
||||
See policy :policy:`CMP0055`.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
cached-regex-clear-fixed
|
||||
------------------------
|
||||
|
||||
* Add :variable:`CMAKE_MATCH_COUNT` for the number of matches made in the last
|
||||
regular expression.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
cmake-E-tar-files-from
|
||||
----------------------
|
||||
|
||||
* The :manual:`cmake(1)` ``-E tar`` command learned a new
|
||||
``--files-from=<file>`` option to specify file names using
|
||||
lines in a file to overcome command-line length limits.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
cmake-E-tar-mtime
|
||||
-----------------
|
||||
|
||||
* The :manual:`cmake(1)` ``-E tar`` command learned a new
|
||||
``--mtime=<date>`` option to specify the modification time
|
||||
recorded in tarball entries.
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
console-pool
|
||||
------------
|
||||
|
||||
* The :command:`add_custom_command` and :command:`add_custom_target`
|
||||
commands learned a new ``USES_TERMINAL`` option to request that
|
||||
the command be given direct access to the terminal if possible.
|
||||
The :generator:`Ninja` generator will places such commands in the
|
||||
``console`` pool. Build targets provided by CMake that are meant
|
||||
for individual interactive use, such as ``install``, are now
|
||||
placed in this pool.
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
cpack-rpm-component-descriptions
|
||||
--------------------------------
|
||||
|
||||
* The :module:`CPackRPM` module learned options to set per-component
|
||||
descriptions and summaries. See the
|
||||
:variable:`CPACK_RPM_<component>_PACKAGE_DESCRIPTION` and
|
||||
:variable:`CPACK_RPM_<component>_PACKAGE_SUMMARY` variables.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
cpack-rpm-pre-post-install
|
||||
--------------------------
|
||||
|
||||
* The :module:`CPackRPM` module learned options to specify
|
||||
requirements for pre- and post-install scripts. See the
|
||||
:variable:`CPACK_RPM_PACKAGE_REQUIRES_PRE` and
|
||||
:variable:`CPACK_RPM_PACKAGE_REQUIRES_POST` variables.
|
||||
|
||||
* The :module:`CPackRPM` module learned options to specify
|
||||
requirements for pre- and post-uninstall scripts. See the
|
||||
:variable:`CPACK_RPM_PACKAGE_REQUIRES_PREUN` and
|
||||
:variable:`CPACK_RPM_PACKAGE_REQUIRES_POSTUN` variables.
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
ctest-delphi-coverage
|
||||
---------------------
|
||||
|
||||
* The :command:`ctest_coverage` learned to support Delphi coverage.
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
curl-darwinssl
|
||||
--------------
|
||||
|
||||
* On OS X, commands supporting network communication, such as
|
||||
:command:`file(DOWNLOAD)`, :command:`file(UPLOAD)`, and
|
||||
:command:`ctest_submit`, now support SSL/TLS even when CMake
|
||||
is not built against OpenSSL. The OS X native SSL/TLS
|
||||
implementation is used by default. OS-configured certificate
|
||||
authorities will be trusted automatically.
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
curl-default-cainfo
|
||||
-------------------
|
||||
|
||||
* When CMake is built with OpenSSL on systems other than Windows
|
||||
and OS X, commands supporting network communication via ``https``,
|
||||
such as :command:`file(DOWNLOAD)`, :command:`file(UPLOAD)`, and
|
||||
:command:`ctest_submit`, now search for OS-configured certificate
|
||||
authorities in a few ``/etc`` paths to be trusted automatically.
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
curl-winssl
|
||||
-----------
|
||||
|
||||
* On Windows, commands supporting network communication, such as
|
||||
:command:`file(DOWNLOAD)`, :command:`file(UPLOAD)`, and
|
||||
:command:`ctest_submit`, now support SSL/TLS even when CMake
|
||||
is not built against OpenSSL. The Windows native SSL/TLS
|
||||
implementation is used by default. OS-configured certificate
|
||||
authorities will be trusted automatically.
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
custom-command-byproducts
|
||||
-------------------------
|
||||
|
||||
* The :command:`add_custom_command` and :command:`add_custom_target`
|
||||
commands learned a new ``BYPRODUCTS`` option to specify files
|
||||
produced as side effects of the custom commands. These are not
|
||||
outputs because they do not always have to be newer than inputs.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
feature-record-msvc
|
||||
-------------------
|
||||
|
||||
* The :manual:`Compile Features <cmake-compile-features(7)>` functionality
|
||||
is now aware of features supported by Microsoft Visual Studio (``MSVC``).
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
file-LOCK-command
|
||||
-----------------
|
||||
|
||||
* The :command:`file(LOCK)` subcommand was created to allow CMake
|
||||
processes to synchronize through file and directory locks.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
file-strings-utf-16
|
||||
-------------------
|
||||
|
||||
* The :command:`file(STRINGS)` now supports UTF-16LE, UTF-16BE,
|
||||
UTF-32LE, UTF-32BE as ``ENCODING`` options.
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
find-msmpi
|
||||
----------
|
||||
|
||||
* The :module:`FindMPI` module learned to find MS-MPI on Windows.
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
install-EXPORT-absolute-prefix
|
||||
------------------------------
|
||||
|
||||
* The :command:`install(EXPORT)` command now works with an absolute
|
||||
``DESTINATION`` even if targets in the export set are installed
|
||||
with a destination or usage requirements specified relative to the
|
||||
install prefix. The value of the :variable:`CMAKE_INSTALL_PREFIX`
|
||||
variable is hard-coded into the installed export file as the base
|
||||
for relative references.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
record-GNU-5-features
|
||||
---------------------
|
||||
|
||||
* The :manual:`Compile Features <cmake-compile-features(7)>` functionality
|
||||
is now aware of features supported by GNU compiler version 5.0.
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
rpm_multi_prefix
|
||||
----------------
|
||||
|
||||
* The :module:`CPackRPM` module learned a new
|
||||
:variable:`CPACK_RPM_<COMPONENT>_PACKAGE_PREFIX` variable to
|
||||
specify a component-specific value to use instead of
|
||||
:variable:`CPACK_PACKAGING_INSTALL_PREFIX`.
|
||||
|
||||
* The :module:`CPackRPM` module learned a new
|
||||
:variable:`CPACK_RPM_RELOCATION_PATHS` variable to
|
||||
specify multiple relocation prefixes for a single rpm package.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
try-run-link-libraries
|
||||
----------------------
|
||||
|
||||
* The :command:`try_run` command learned to honor the ``LINK_LIBRARIES``
|
||||
option just as :command:`try_compile` already does.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
try_compile-link-flags
|
||||
----------------------
|
||||
|
||||
* The :command:`try_compile` command source file signature now honors
|
||||
link flags (e.g. :variable:`CMAKE_EXE_LINKER_FLAGS`) in the generated
|
||||
test project. See policy :policy:`CMP0056`.
|
||||
|
|
@ -1,22 +0,0 @@
|
|||
unsupported-compilers
|
||||
---------------------
|
||||
|
||||
* The implementation of CMake relies on some C++ compiler features which are
|
||||
not supported by some older compilers. As a result, those old compilers
|
||||
can no longer be used to build CMake itself. CMake continues to be able to
|
||||
generate Makefiles and project files for users of those old compilers
|
||||
however. The compilers known to no longer be capable of building CMake
|
||||
are:
|
||||
|
||||
* MSVC 6 and 7.0 - superceded by VisualStudio 7.1 and newer compilers.
|
||||
* GCC 2.95 - superceded by GCC 3 and newer compilers.
|
||||
* Borland compilers - superceded by other Windows compilers.
|
||||
* Compaq compilers - superceded by other compilers.
|
||||
* Comeau compilers - superceded by other compilers.
|
||||
* SGI compilers - IRIX was dropped as a host platform.
|
||||
|
||||
When building using SolarisStudio 12, the default ``libCStd`` standard
|
||||
library is not sufficient to build CMake. The SolarisStudio distribution
|
||||
supports compiler options to use ``STLPort4`` or ``libstdc++``. An
|
||||
appropriate option to select the standard library is now added
|
||||
automatically when building CMake with SolarisStudio compilers.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
vs-nsight-tegra-min-api
|
||||
-----------------------
|
||||
|
||||
* A :prop_tgt:`ANDROID_API_MIN` target property was introduced to
|
||||
specify the minimum version to be targeted by the toolchain.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
vs-shader-flags
|
||||
---------------
|
||||
|
||||
* A :prop_sf:`VS_SHADER_FLAGS` source file property was added to specify
|
||||
additional shader flags to ``.hlsl`` files, for the Visual Studio generators.
|
||||
|
|
@ -1,22 +0,0 @@
|
|||
windows-utf-8
|
||||
-------------
|
||||
|
||||
* On Windows, CMake learned to support international characters.
|
||||
This allows use of characters from multiple (spoken) languages
|
||||
in CMake code, paths to source files, configured files such as
|
||||
``.h.in`` files, and other files read and written by CMake.
|
||||
Because CMake interoperates with many other tools, there may
|
||||
still be some limitations when using certain international
|
||||
characters.
|
||||
|
||||
Files written in the :manual:`cmake-language(7)`, such as
|
||||
``CMakeLists.txt`` or ``*.cmake`` files, are expected to be
|
||||
encoded as UTF-8. If files are already ASCII, they will be
|
||||
compatible. If files were in a different encoding, including
|
||||
Latin 1, they will need to be converted.
|
||||
|
||||
The Visual Studio generators now write solution and project
|
||||
files in UTF-8 instead of Windows-1252. Windows-1252 supported
|
||||
Latin 1 languages such as those found in North and South America
|
||||
and Western Europe. With UTF-8, additional languages are now
|
||||
supported.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
xcode-revise-make-program
|
||||
-------------------------
|
||||
|
||||
* The :generator:`Xcode` generator no longer requires a value for
|
||||
the :variable:`CMAKE_MAKE_PROGRAM` variable to be located up front.
|
||||
It now locates ``xcodebuild`` when needed at build time.
|
||||
|
|
@ -13,5 +13,6 @@ Releases
|
|||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
3.2.0 <3.2.0>
|
||||
3.1.0 <3.1.0>
|
||||
3.0.0 <3.0.0>
|
||||
|
|
|
|||
Loading…
Reference in New Issue