GitLab

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

This content was copied from another test where both the Core and Gui
targets are used.

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

This should not have survived in commit a247911a (Tests: Don't read
the LOCATION property from build targets., 2013-11-18).

As C++11, python, D and java do.

 http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3472.pdf

Add test for uppercase hex literals.

The other infrastructure for transitive property handling is
already using a preprocessor loop.

Implement special backward-compatibility handling of
COMPILE_DEFINITIONS_<CONFIG> using a template switch for the
extra check.

Introduce a new set of macros to select the column.

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

84fac67f Don't allow include() of export(EXPORT) file at configure time.
faedd2be cmTarget: Fix system include annotation propagation.
9eb06d0d add_library: Disallow invalid signatures for INTERFACE_LIBRARY.
10d65d50 cmTarget: Move a variable initialization closer to where it is used.
0f3e8e95 Undefine local preprocessor loop variables.
9ba47ee4 Genex: Reform error-checking for nullary/unary expressions.
fa651c7a cmTarget: Remove some of the INTERFACE_LIBRARY whitelisted properties.
61d138ae cmTarget: INTERFACE_LIBRARY is always EXCLUDE_FROM_ALL.
3429541e export: Rename some variables to reflect content type.
7461d67c cmTarget: Enable convenient include dir handling for INTERFACE_LIBRARY.
7fc6e3d6 cmTarget: Remove dead code.
2af966d9 Genex: Add EQUAL expression.
2d663800 cmTarget: Use strtol for numeric parsing.

As a new feature it does not need to participate in CMP0024.

Store cmExportBuildFileGenerator instances which correspond to the
export(EXPORT) signature in a second map which does not own the
pointers.  This avoids the need to add cmExportBuildFileGenerator
and dependencies to the bootstrap system.

Direct users of IMPORTED targets treat INTERFACE_INCLUDE_DIRECTORIES
as SYSTEM, after commit a63fcbcb (Always consider includes from IMPORTED
targets to be SYSTEM., 2013-08-29).  It was intended that transitive
use of an IMPORTED target would have the same behavior, but that
did not work.  The implementation processed only direct dependencies
in cmTarget::FinalizeSystemIncludeDirectories.

Implement transitive evaluation of dependencies by traversing the
link interface of each target in the link implementation.

Document the valid signatures. Add a test for the IMPORTED GLOBAL
signature.

This is more readable and easier to reason about.

Most occurances of this pattern already contain the undef, so add it to
the rest too.

The error messages were incorrect (reporting that the expression
requires one or two parameters), and repeated.  Remove the now-unused
ZeroOrMoreParameters enum value.

There is no need to allow EXCLUDE_* properties, because an
INTERFACE_LIBRARY has no direct build output.

IMPORTED_LINK_INTERFACE_LANGUAGES are relevant only to static
libraries.

VERSION is relevant only to the filename of direct build outputs,
which INTERFACE_LIBRARY does not have.

This method is used with a list of languages.

Make the CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE variable affect
INTERFACE_LIBRARY targets.

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: Workaround pygments reporting an error for genexes.
...

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.