GitLab

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.

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)

Note in a few places of the cmake_policy() command documentation
that the cmake_minimum_required() command can set policies too.
Inspired-by: Peter Kümmel <syntheticpp@gmx.net>

Add reStructuredText markup manually to improve formatting of the
documentation.  Organize the documentation into subsections.

Brad King authored May 30, 2014 and Kitware Robot committed May 30, 2014

fb2fa476 Genex: Clarify error message on use with non-binary targets (#14899).

Extend the ctest(1) manual with a section describing configuration
and usage of CTest as a CDash software quality dashboard client.

Describe the behavior of the ctest_start() command when the
CTEST_CHECKOUT_COMMAND or CTEST_CVS_CHECKOUT variable is set.

Brad King authored May 29, 2014 and Kitware Robot committed May 29, 2014

c4af46b4 add_custom_command: Normalize OUTPUT and DEPENDS paths.

Brad King authored May 29, 2014 and Kitware Robot committed May 29, 2014

21ec5f84 CPackDeb: Invoke "dpkg-shlibdeps --version" with C locale

Brad King authored May 29, 2014 and Kitware Robot committed May 29, 2014

b684ce58 VS: Use lower-case boolean values in VS 7-9 (#14927)

Brad King authored May 29, 2014 and Kitware Robot committed May 29, 2014

f49b6a33 FindDoxygen: Deprecate DOXYGEN_DOT_PATH
7980eab8 FindDoxygen: Improve search for Graphviz "dot" on Windows

Brad King authored May 29, 2014 and Kitware Robot committed May 29, 2014

dd043c3f Features: Add support for C++14 features.

Mark Salisbury authored May 22, 2014 and Brad King committed May 28, 2014

The VS 7-9 IDEs parse .vcproj file boolean values in lower or upper
case.  The .NET XML parsing chokes on anything but "true", "false", "0",
"1".  Teach our generators to use lower-case names since they will work
for both parsers.  Our VS >= 10 flag tables already use lower-case.

While tracing dependencies of a target, cmTargetTraceDependencies
follows sources by full path to determine if the source is to be
produced by a custom command.  Commit 4959f341 (cmSourceFileLocation:
Collapse full path for directory comparisons., 2014-03-27) changed
the storage of target sources to be in the form of a normalized
path instead of an unnormalized path.

The path is followed by looking it up in a mapping via
cmMakefile::GetSourceFileWithOutput to acquire an appropriate
cmSourceFile.  The mapping is populated with the OUTPUT components
of add_custom_command invocations, however it is populated with
unnormalized paths.  This means that the tracing logic does not
find appropriate cmSourceFiles, and does not generate appropriate
build rules for the generated sources.

Normalize the paths in the OUTPUT components of add_custom_command
to resolve this.

The paths in the DEPENDS component of add_custom_command are also
not normalized, leading to the same problem again.  Normalize the
depends paths after generator evaluation and expansion.

Brad King authored May 28, 2014 and Kitware Robot committed May 28, 2014

deee7c42 CTest: Fix Python coverage.py off-by-one error in results
88b3dcb1 CTest: Improve Python coverage.py source file search algorithm

Brad King authored May 28, 2014 and Kitware Robot committed May 28, 2014

d0b1d2a6 CPackWiX: Implement CPACK_NEVER_OVERWRITE and CPACK_PERMANENT properties
15a8af21 Add an "installed file" property scope

Brad King authored May 28, 2014 and Kitware Robot committed May 28, 2014

58f7baab FindFreetype: Indent with 2 spaces instead of 4
444f8801 FindFreetype: Use lower-case name in call to FPHSA
836a28d5 FindFreetype: Move PATH_SUFFIXES argument for more consistency
4ad6dace FindFreetype: Add newlines to reduce code width

Brad King authored May 28, 2014 and Kitware Robot committed May 28, 2014

668e571d GNUtoMS: Add support for VS 2013 (#14936)

Brad King authored May 28, 2014 and Kitware Robot committed May 28, 2014

1cd37527 cmCacheManager: Avoid cache entry self-assignment
326d15a3 cmake: Tolerate missing HELPSTRING on compiler change

Nils Gladitz authored May 15, 2014 and Brad King committed May 28, 2014

Teach set_property and get_property an "INSTALL" property type to be
associated with install-tree file paths.  Make the properties available
to CPack for use during packaging.  Add a "prop_inst" Sphinx domain
object type for documentation of such properties.

Zach authored May 27, 2014 and Brad King committed May 28, 2014

The cobertura format uses line numbers indexed starting at 1, and CTest
uses a vector indexed starting at 0 to store them.

Roni Choudhury authored May 24, 2014 and Brad King committed May 28, 2014

If the coverage.py source file is not found in the source directory, the
build directory is first searched before raising an error.

This is necessary because it is a valid workflow to build a Python
package from source, then install this package to a virtualenv that
lives in the build directory.  Tests will run against this deployed
package and therefore the covered source files will be found in a
subdirectory of the build directory, and not anywhere in the source
directory.

The version message is localized and may not match when a non-english locale is in use.