GitLab

Whitelisting of properties already ensures that the LOCATION
property will not be read from an INTERFACE_LIBRARY.

Support decimal, hex, octal and binary literals.

On Windows apparently sscanf can not handle hex numbers.

Test that numeric comparison works with hex numbers.

Brad King authored Jan 06, 2014 and Kitware Robot committed Jan 06, 2014

a55c70de cmTarget: Remove support for <CONFIG>_LOCATION property.
c9f9b3cd cmTarget: Test impliedByUse number-compatible properties.
fbe1fa72 cmTarget: Don't repeat property origin debug information.
01c545c5 cmTarget: Fix debug report for interface-set compatibility types.
c67e1a6a cmTarget: Fix reporting interface-set properties which are FALSE.
07b0f546 Qt Tests: Remove commented and unneeded line.
79db8ef7 cmTarget: Fix the property compatibility error message
43340a9c Help: Reformat Qt autogenerator documentation.
d98ea6c0 Help: Mark some code blocks as containing cmake code.
ea78935f GenerateExportHeader: Reformat docs.
272a20f8 cmTarget: Don't update IMPORTED target compilation properties
03d842a9 Run the add_compile_options command unit test.
cd3d0b61 get_property: Fix testing ALIASED_TARGET target property (#14670)
6a622285 install: Ensure that install(TARGETS) works with no DESTINATION
af3d3b88 export: Only generate and install configuration files if needed.
0de81bba Help: Workaroun...

Brad King authored Jan 06, 2014 and Kitware Robot committed Jan 06, 2014

0d9cdab9 Help: Add cmake-buildsystem.7 manual

Brad King authored Jan 06, 2014 and Kitware Robot committed Jan 06, 2014

9e41eb68 Fix wording of "the the" typos throughout text

Brad King authored Jan 06, 2014 and Kitware Robot committed Jan 06, 2014

196cee67 Merge branch 'upstream-kwsys' into update-kwsys
4709c7ad KWSys 2014-01-02 (606d7d6f)

Brad King authored Jan 06, 2014 and Kitware Robot committed Jan 06, 2014

e6b0f452 Eclipse: use MachO64 parser starting with Helios (#14380)

Stephen Kelly authored Jan 04, 2014 and Brad King committed Jan 06, 2014

Describe how to define a buildsystem of binary targets, how to
express dependencies between them, how to add build specifications,
how to specify usage requirements, transitive and compatible
propagation and the various pseudo targets.

It is not documented, is very old, is compatibility code,
is non-uniform and is not needed.

Test that it is an error to read a number-compatible property to
determine the link implementation.  An alternative would be to
consider the value to be "0", however, that is too arbitrary
given the use-cases of this feature.  Values from this feature may
be used in setting a define, where "0" may have special or invalid
meaning and should be explicit.

If the dependent target sets the property to boolean false, ensure
that that appears in the debug report.  Previously, the report
output contained whether the property was consistent among dependencies,
displaying 'TRUE', instead of the content of the property, which may
be 'FALSE'.

Return a std::pair from the consistentProperty method.  This makes
it possible to make the return value for string types easier to
reason about.  The return value of consistentProperty was previously
set to an empty static string to emulate a 'true' value for the caller
in commit 816b4a8a (cmTarget: Make consistentProperty
return consistent content., 2013-10-22).  The pair makes the
consistency result properly typed.

Don't refer to 'both', but a 'mixture'. List all compatible interface
property types possible.

Add another test for a mixture of three compatibilities.

The include_directories() and add_compile_options() commands
should not append to the corresponding target property for IMPORTED
targets.  This is already the case for add_definitions().

This has not been executed since it was added in
commit a984f325 (Introduce add_compile_options command., 2013-06-04).

In the case where the argument is not an ALIAS, the variable should
be set to a -NOTFOUND content.

INTERFACE_LIBRARY targets have no corresponding files, and so
require no DESTINATION to install anything to.

The modern way to create configuration dependent content is using
generator expressions in the main export file.  The only non-deprecated
property still generated in the configuration-specific files are
IMPORTED_LOCATION_<CONFIG>

INTERFACE_LIBRARY targets have no location, and no need for those
files.

Without the workaround, CMake code snippets are not highlighted
at all because pygments can not lex the generator expressions.

The requirement was updated in commit 920ffbf5 (Require CMake 2.8.4
or greater to build CMake, 2013-10-11) and similar snippets were
removed.

Don't erroneously name it for the link implementation. That's
something different.

The next version is 3.0.0, not 2.8.13.

The version generated in the export file should be updated in
the release branch in both cmExportInstallFileGenerator and
cmExportBuildFileGenerator.

Kitware Robot authored Jan 02, 2014 and Brad King committed Jan 03, 2014

Extract upstream KWSys using the following shell commands.

$ git archive --prefix=upstream-kwsys/ 606d7d6f | tar x
$ git shortlog --no-merges --abbrev=8 --format='%h %s' e81f2a9e..606d7d6f
Muli Baron (1):
      606d7d6f Terminal: Add putty-256color as a VT100 color-capable terminal

Change-Id: Ibd80e7b209c29947c384023d3ac1ce862648de01

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

98b9f52b Help: Document export(EXPORT) in the cmake-packages manual.
a1d2bda2 Don't copy find_dependency in configure_package_config_file.
f4f65293 Help: cmake-packages: Add missing slash.
cbe7e8fa export: Implement EXPORT subcommand (#9822)

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

33fa10f6 cmake-mode.el: Add autoload cookies
d03a0fb4 cmake-mode.el: Move header line to the top of file

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

37104d97 kate: put full path to cmake into comment
424d5dc0 kate: support also the build plugin in kate <= 4.12
8bd6cf0f kate: the prev_target is not used by kate