| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
df71f96 get_filename_component: Document path components more clearly (#14091)
|
| |
| |
| |
| |
| | |
Organize component names in a table to explain each in more detail.
Clearly state that PATH is the directory name.
|
|\ \
| | |
| | |
| | |
| | | |
ce441fa try_compile: add missing fclose() to recently added error case
|
| |/
| |
| |
| |
| |
| |
| |
| | |
In commit 236133e7 (Handle targets in the LINK_LIBRARIES of try_compile,
2013-02-09) an error return case was added without closing the file in
progress. Add the missing fclose() call.
Spotted by sevenhill.
|
|\ \
| | |
| | |
| | |
| | | |
5a5e0fa Fix clearing of the INCLUDE_DIRECTORIES DIRECTORY property.
|
| | |
| | |
| | |
| | |
| | | |
This was broken by commit 18a3195a (Keep track of INCLUDE_DIRECTORIES
as a vector of structs., 2012-11-19).
|
| |/
|/| |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
6c613b4 Handle usr-move without forcing absolute paths (#14041)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/ |
|
| |
|
|\
| |
| |
| |
| | |
20c99b1 automoc: Use a pre-build event in VS >= 7
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
|\ \
| | |
| | |
| | |
| | | |
de13d68 add_dependencies: Distinguish target v. file dependencies in error (#14050)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
|
| | | |
|
| | | |
|
| |/
|/| |
|
|/ |
|
|\
| |
| |
| |
| | |
674f918 cmSystemTools: Generalize TrimWhitespace to all whitespace
|
| |
| |
| |
| |
| | |
Modify cmSystemTools::TrimWhitespace() to remove all leading and
trailing whitespace, not just spaces.
|
|\ \
| | |
| | |
| | |
| | | |
634bb33 Error if linked target has relative paths in INTERFACE_INCLUDE_DIRECTORIES
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
|
| |/
|/| |
|