Brad King authored Apr 04, 2013 and Kitware Robot committed Apr 04, 2013

6c613b43 Handle usr-move without forcing absolute paths (#14041)

Brad King authored Apr 03, 2013 and Kitware Robot committed Apr 03, 2013

bec8e64c Qt4: Fix typo setting a variable for FindThreads.

In commit 0c727b90 (install(EXPORT): Force absolute paths for usr-move,
2013-03-08) and commit d4774140 (configure_package_config_file: force
absolute paths for usr-move, 2013-01-24) we supported Linux
distributions implementing the "/usr move" by assuming that installation
to (/usr)?/lib(64)? represents a non-relocatable system package.

When cross-compiling one may prepare a package for installation into a
system location on a target machine but install the package files on the
*host* machine inside another path for use with CMAKE_FIND_ROOT_PATH.
In this case the package development files must still be relocatable.

Handle "/usr move" with a new approach that works with relocatable
files.  Teach configure_package_config_file and install(EXPORT) to
generate special logic in a package configuration file or targets file
for installation under (/usr)?/lib(64)?.  Teach the file to recognize
when it is loaded through a symlink that refers to the same realpath as
its original install destination.  In such a case, use the original
install prefix.  Otherwise, compute the prefix relative to the current
file location to make it relocatable.

Brad King authored Apr 02, 2013 and Kitware Robot committed Apr 02, 2013

20c99b1d automoc: Use a pre-build event in VS >= 7

Brad King authored Apr 02, 2013 and Kitware Robot committed Apr 02, 2013

de13d68d add_dependencies: Distinguish target v. file dependencies in error (#14050)

Fixes bug 14055.

In VS IDE generators add a pre-build event to perform automoc instead of
using a separate custom target.  This reduces the number of targets in the
.sln that need to be loaded by the IDE.

This also works around a VS 11 bug as discussed in issue 13900.

Suggested-by: Hauke Heibel <hauke.heibel@gmail.com>

When called with a non-existent LHS target name the user may be trying
to add file-level dependencies.  Clarify the error message to explain
the difference between target-level and file-level dependencies.  Point
the reader at the commands and options needed for the latter.

Brad King authored Mar 28, 2013 and Kitware Robot committed Mar 28, 2013

674f918a cmSystemTools: Generalize TrimWhitespace to all whitespace

Brad King authored Mar 28, 2013 and Kitware Robot committed Mar 28, 2013

535e53c7 Fix the Qt 5 version required to run the IncompatibleQt test.

Brad King authored Mar 28, 2013 and Kitware Robot committed Mar 28, 2013

634bb33f Error if linked target has relative paths in INTERFACE_INCLUDE_DIRECTORIES

Brad King authored Mar 28, 2013 and Kitware Robot committed Mar 28, 2013

5479251b Modules/readme.txt: make lines a bit shorter for easier readability
140692d8 Modules/readme.txt: switch from "XXX" to "Xxx"

Brad King authored Mar 28, 2013 and Kitware Robot committed Mar 28, 2013

8a2fca8c UseJava.cmake: require explicit request to include jars

Brad King authored Mar 28, 2013 and Kitware Robot committed Mar 28, 2013

4d668f33 Clang: Add -isystem flag support everywhere

Alexander Neundorf authored Mar 26, 2013 and Brad King committed Mar 28, 2013

This patch doesn't make them 79 characters long, but at least gets rid
of really long lines.  While at it, fix spelling of "relevant".

Alex

Alexander Neundorf authored Mar 26, 2013 and Brad King committed Mar 28, 2013

Using XXX as name of the package is ambiguous, since it can be
interpreted as "ALLUPPERCASE" and also as "ExactCase (if the name
is already ALLUPPERCASE)".
After extensive discussion there is the conclusion that ExactCase
is intended, so using a CamelCased name makes that more obvious.

Alex

Matthew Woehlke authored Mar 26, 2013 and Brad King committed Mar 28, 2013

Modify add_jar to (partly) use cmake_parse_arguments, and to require
using the named argument list INCLUDE_JARS to specify jar files (or jar
targets) to use as dependencies when creating a jar. This preserves the
ability to have such, while restoring the historic behavior that jar
files listed as sources are ignored. (The code now explicitly ignores
them, however, rather than adding them to an unused local variable, so
that it is more clear that nothing is being done with them.)

Ben Boeckel authored Mar 26, 2013 and Brad King committed Mar 28, 2013

In GNU.cmake, -isystem is not used if APPLE is set. However, Clang has
pretty much always supported -isystem, so we should always use it.

In the future, GNU.cmake should do a version check to see if -isystem is
supported.

Petr Kmoch authored Mar 27, 2013 and Brad King committed Mar 27, 2013

Modify cmSystemTools::TrimWhitespace() to remove all leading and
trailing whitespace, not just spaces.

The commit to add the INTERFACE_QT_MAJOR_VERSION in qtbase.git
is 14054d45 (Set the INTERFACE_QT_MAJOR_VERSION to 5., 2013-03-16)
which will be part of Qt 5.1.0.

If there is a Qt 5.0.3 release, there is no guarantee it will
contain that commit. Make sure such a Qt version does not fail
with this test if not.

We can do this check only if the TargetName is non-empty, which means
that we're evaluating INTERFACE_INCLUDE_DIRECTORIES from a linked
dependency which was set using target_link_libraries.

It is possible to have relative paths in INCLUDE_DIRECTORIES already
in CMake 2.8.10.2, so that part will require a policy to fix.

Brad King authored Mar 26, 2013 and Kitware Robot committed Mar 26, 2013

28051f11 Report an error on IMPORTED targets with a faulty INTERFACE
af81a3c3 install(EXPORT): Ensure clean INTERFACE_INCLUDE_DIRECTORIES

Brad King authored Mar 26, 2013 and Kitware Robot committed Mar 26, 2013

118f741c ExternalProject: Retry on a failed git clone

Brad King authored Mar 26, 2013 and Kitware Robot committed Mar 26, 2013

c677838c VS: Fix VS 10/11 .sln headers (#14038)

Brad King authored Mar 26, 2013 and Kitware Robot committed Mar 26, 2013

2e80f9f2 Fix new target commands documentation.

Brad King authored Mar 26, 2013 and Kitware Robot committed Mar 26, 2013

1703b00c Test evaluation of per-config COMPILE_DEFINITIONS (#14037)
a6286e92 Fix the evaluation of per-config COMPILE_DEFINITIONS (#14037)

Stephen Kelly authored Mar 24, 2013 and Brad King committed Mar 26, 2013

It is considered an error if the INTERFACE_INCLUDE_DIRECTORIES contains
a directory which does not exist, which indicates a programmer error
by the upstream, or a packaging error.

One of the RunCMake.CompatibleInterface tests also needs to be updated
due to this change. Non-existant includes were used in the test, but
are not needed.

Stephen Kelly authored Mar 24, 2013 and Brad King committed Mar 26, 2013

Check that source and binary directories are not part of the
INTERFACE_INCLUDE_DIRECTORIES for installed IMPORTED targets.

This is limited to directories which do not contain generator
expressions to evaluate. Such paths can only be checked at time
of use of the imported target, which will be done in a follow up
patch.

Bill Hoffman authored Mar 20, 2013 and Brad King committed Mar 26, 2013

Git sometimes fails to clone repositories due to network outage or
server load.  Try 3 times before giving up.