GitLab

Delay use of CMAKE_GENERATOR_TOOLSET until the CMakeSystem.cmake
file has been configured and loaded during the first project() or
enable_language() command.  This gives the toolchain file named by
CMAKE_TOOLCHAIN_FILE a chance to set CMAKE_GENERATOR_TOOLSET.  This
point is still early enough to set the generator toolset prior to
the initialization of any languages that might use the toolset.

The cmake::GeneratorToolset member variable remains an indication
of what was specified by the -T option or loaded from the cache.
It does not need to be updated based on the toolchain file setting.
The cmMakefile::TryCompile can still pass cmake::GeneratorToolset
into the inner instance because the try-compiled project will do
platform and language initialization using the CMakeSystem module
configured for the outer project.

Extend the RunCMake.GeneratorToolset test with cases that use a
toolchain file to set CMAKE_GENERATOR_TOOLSET.

Divide the cmGlobalVisualStudio10Generator "PlatformToolset" member into
two members representing the generator-selected default toolset and the
user-specified CMAKE_GENERATOR_TOOLSET value.  Prefer the user-specified
value, if any, and then fall back to the generator-selected default.

The latter matches with CMAKE_GENERATOR_TOOLSET better.

Brad King authored Jun 04, 2014 and Kitware Robot committed Jun 04, 2014

44e2923f cmake: Fix --build crash on bad CMAKE_GENERATOR in cache

Brad King authored Jun 03, 2014 and Kitware Robot committed Jun 03, 2014

34c6fd3a Help: Convert CTest Script variable references to cross-references
de710f37 Help: Add placeholder documents for CTest Script variables

In the ctest(1) manual and ctest_start() command documentation, convert
mentions of CTest Script variables to cross-references so they will be
rendered as links.

Provide a minimal explanation of each variable by simply naming
the corresponding ctest(1) setting and linking to the ctest(1)
manual.

If we fail to create the generator named by CMAKE_GENERATOR, exit
with an error message instead of crashing.  While at it, fix the
wording of the error message when CMAKE_GENERATOR is not set.

Extend the RunCMake.CommandLine test with cases covering the
"cmake --build" option when the named directory does not provide
a CMakeCache.txt with a valid CMAKE_GENERATOR.

Brad King authored Jun 03, 2014 and Kitware Robot committed Jun 03, 2014

889f2fd8 Simplify and clarify credit text and link

Use the name "Kitware" rather than "Kitware, Inc." to simplify the text.
Provide a CMake-specific URL.

Brad King authored Jun 03, 2014 and Kitware Robot committed Jun 03, 2014

8da0a75b Simplify and clarify credit text and link

Use the name "Kitware" rather than "Kitware, Inc." to simplify the text.
Provide a CMake-specific URL.

Brad King authored Jun 03, 2014 and Kitware Robot committed Jun 03, 2014

907e422b Help: Explain build/install-tree include dirs in more places (#14946)

Brad King authored Jun 02, 2014 and Kitware Robot committed Jun 02, 2014

06ab7db3 FindQt4: Use standard section header underline convention

The FindQt4 module is a CMake Domain object of type "module".
Our convention for domain object document titles is "------"
and domain object document sections is "^^^^^^".  Switch to
these within the FindQt4 documentation.

Brad King authored Jun 02, 2014 and Kitware Robot committed Jun 02, 2014

793b64e4 Help: Document section header underline hierarchy in cmake-developer.7
05bd31ab Help: Organize documentation style sections in cmake-developer.7
eaafe756 Help: Add documentation style section headers to cmake-developer.7
4207b3a3 Help: Use "^^^^" for subsubsection headers

Explicitly specify the sequence of underline characters we use in the
CMake documentation.  It is the same sequence as that suggested in the
Sphinx documentation, but we have our own descriptions.

Now that the style guidelines have section titles instead of numbers,
organize them into more well-defined sections.

Give the style guides titles instead of numbers so we can link to them.

This is the convention suggested in the Sphinx documentation and is
already used in several other places in the CMake documentation.
Update a few places where we were using other characters.

Explain how to use $<BUILD_INTERFACE> and $<INSTALL_INTERFACE> directly
in the documentation of the target_include_directories command and
INTERFACE_INCLUDE_DIRECTORIES target property.  Otherwise readers need
to notice the link to the cmake-buildsystem(7) manual and find the
example in that to understand the need for these expressions.

Also fix the explanation in cmake-buildsystem(7) to not claim that
relative paths may be used inside a BUILD_INTERFACE expression.

Brad King authored Jun 02, 2014 and Kitware Robot committed Jun 02, 2014

60a981ea Features: Enable compiler extensions by default.

Brad King authored Jun 02, 2014 and Kitware Robot committed Jun 02, 2014

2d57a390 Help: Document ctest dashboard client usage
28f73dff Help: Document ctest_start initial checkout command variables

Brad King authored Jun 02, 2014 and Kitware Robot committed Jun 02, 2014

b1f4e620 Help: Reference cmake_minimum_required from cmake_policy docs
69a23cb2 Help: Format cmake_policy command documentation
0c4835a3 Help: Add missing space in policy CMP0020 description

Brad King authored Jun 02, 2014 and Kitware Robot committed Jun 02, 2014

6fbd9a8f Help: Add code example for INSTALL_INTERFACE to cmake-buildsystem.

Compilers enable their extensions by default, and disabling them
implicitly can lead to results which are surprising or non-obvious
to debug.

 http://public.kitware.com/pipermail/cmake-developers/2014-May/010575.html
 http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/10214
 https://www.mail-archive.com/cmake-developers@cmake.org/msg10116.html
 (Compiler feature extensions by default, 29 May 2014)