| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
d25ad48 OS X: Add CMP0042 to enable MACOSX_RPATH by default
|
| |
| |
| |
| |
| | |
Also adding documentation for CMAKE_MACOSX_RPATH, and improving
documentation for MACOSX_RPATH.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Revise the organization introduced in commit 2c7cd95c (Help: Organize
top-level index, 2013-10-28) to drop "Other Manuals" and put them in
"Reference Manuals" because the distinction between them has blurred.
Perhaps a better breakdown of the reference manuals will emerge in
the future.
While at it, sort the reference manual toctree by name.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
3fe4ac8 Help: Add a CMake manual for Packages related docs.
20cafa2 Split the find_dependency macro into a separate file.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This allows Config file authors to use it without having to use
CONFIGURE_PACKAGE_CONFIG_FILE.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
8f849b9 Help: Mention if(POLICY) and NO_POLICY_SCOPE in policies manual.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
0227ece Help: Clarify CMAKE_VERBOSE_MAKEFILE initialization (#14658)
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
Explain that it is initialized to false by the project() command and
intended for configuration by the end user performing a build.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
INTERFACE libraries may not use double-colons, but IMPORTED
targets may.
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
6b8662e Help: Clarify if(TARGET) behavior (#14646)
b74819e Help: Format 'if' command documentation
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Define the meaning of a "target" clearly and link to the commands
that create them.
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
Manually update reStructuredText formatting. Use a definition list
for the possible if() tests supported. Add inline literal markup
as appropriate. Also make minor wording tweaks to make it flow
better with the new markup.
|
|/ /
| |
| |
| | |
Link to other properties mentioned in the docs already.
|
| |
| |
| |
| |
| | |
Refine the .rst formatting. Document the FILES option explicitly
and specify how it treats relative paths.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
259bf09 Make the cmStrictTargetComparison operate on const cmTarget*.
8cc3cdb Help: Fix up the VISIBILITY_INLINES_HIDDEN docs.
1396ab8 Don't generate self-references for system include directories.
|
| | |
| | |
| | |
| | |
| | | |
Resolve some sentence fragments, remove a copy-pasto from other docs
and use a link to the CMAKE_VISIBILITY_INLINES_HIDDEN variable.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
e420124 CMakeDetermineCompilerId: Use CMAKE_VS_(DEVENV|MSBUILD|MSDEV)_COMMAND
0c55729 VS: Add CMAKE_VS_(DEVENV|MSBUILD|MSDEV)_COMMAND variables
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Since commit 5f5c92b9 (VS: Add internal APIs to find MSBuild,
devenv/VCExpress, and msdev, 2013-11-13) the VS generators have
known how to lookup the locations of their build tools directly.
Expose this information to CMake language code by defining new
variables to hold the paths to these tools.
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
c45b5ce Help: Add cmake-toolchains.7 manual
3e3f8b4 Help: Document the CMAKE_FIND_ROOT_PATH* variables.
531c108 Help: Document the CMAKE_TOOLCHAIN_FILE.
|
| | | |
| | | |
| | | |
| | | | |
Create a manual for toolchain related docs.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Add a replacement template for the variables, and link to them from
the documentation for the find_* commands.
|
| | |/
| |/|
| | |
| | | |
Link to the new docs from existing references to the variable.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
c0897cf Help: Document PDB behavior w.r.t. static libraries explicitly (#14600)
09c05f3 Help: Format PDB_NAME and PDB_OUTPUT_DIRECTORY documentation
cb7b907 Help: Document CMAKE_PDB_OUTPUT_DIRECTORY_<CONFIG> variable
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Document PDB_NAME and PDB_OUTPUT_DIRECTORY as applying only to shared
libraries and executables. Add an explicit note to explain why they
do not work for static libraries.
|
| | | |
| | | |
| | | |
| | | | |
Add reStructuredText inline markup.
|
| |/ / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
98093c4 QtAutoUic: Add INTERFACE_AUTOUIC_OPTIONS target property.
02542b4 QtAutoUic: Handle new -include command line parameter.
1242f4e Genex: Add {UPPER,LOWER}_CASE and MAKE_C_IDENTIFIER.
754b321 QtAutogen: Use config without prefix in map key.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Transitively consume the property from linked dependents.
Implement configuration-specific support by following the pattern
set out for compile definitions and includes in cmQtAutoGenerators.
Implement support for origin-tracking with CMAKE_DEBUG_TARGET_PROPERTIES.
This is motivated by the needs of KDE, which provides a separate
translation system based on gettext instead of the Qt linguist
translation system. The Qt uic tool provides command line options
for configuring the method used to translate text, and to add an
include directive to the generated file to provide the method.
http://thread.gmane.org/gmane.comp.kde.devel.frameworks/7930/focus=7992
Implement the interface to provide the uic options as a usage-requirement
on the KI18n target, as designed for KDE.
|
| |/ / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
5838aba Export: Report error on relative include with genex.
7a3e45b Export: Prefix relative items with genexes in INSTALL_INTERFACE.
f088a32 Export: Process INSTALL_INTERFACE in INCLUDES DESTINATION.
9eedc85 Export: Process relative includes after genex evaluation.
80790f3 Export: Test existing behavior of exporting includes with genexes.
38afc82 target_include_directories: Allow relative path with genex
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Diagnostics which check the sanity of exported include paths
previously skipped over any path containing a generator expression.
Introduce a policy to issue an error message in such cases.
The export files created in the OLD behavior are not usable, because
they contain relative paths or paths to the source or build location
which are not suitable for use on installation. CMake will report an
error on import.
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
b54c336 kate: add some documentation
9414217 kate: insert build targets
644e012 kate: add project generator for the Kate project plugin
|
| |/ /
| | |
| | |
| | | |
Alex
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
7605e37 Ninja: job pool support for compiling and linking
|
| |/ /
| | |
| | |
| | |
| | | |
Could be tested by setting the environment
variable NINJA_STATUS=[%r]
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
ebeb31d Help: Fix typo in CMP0040 docs.
97b0abb Help: Fix typo in genex docs.
|
| | | |
| | | |
| | | |
| | | | |
'report and error' -> 'report an error'
|
| |/ /
| | |
| | |
| | | |
would be require -> would require
|
|/ /
| |
| |
| |
| | |
Test this by generating files with a custom target, which moc
requires to be present when it is run.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Move "extra" generators to their own section instead of duplicating them
for each corresponding main generator. Divide the list of main
generators into command-line and IDE sections and sort the names within
each section. Document the environment from which each kind of
generator may be used.
Add a section to each "extra" generator documenting which main
generators may be used with it.
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
7521da2 Introduce CMAKE_STAGING_PREFIX variable.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This variable can be useful in cross-compiling contexts where the
sysroot is read-only or where the sysroot should otherwise remain
pristine.
If the new CMAKE_STAGING_PREFIX variable is set, it is used instead
of CMAKE_INSTALL_PREFIX when generating the installation rules in
cmake_install.cmake.
This way, the CMAKE_INSTALL_PREFIX variable
always refers to the installation prefix on the target device, regardless
of whether host==target.
If any -rpath paths passed to the linker contain the CMAKE_STAGING_PREFIX,
the matching path fragments are replaced with the CMAKE_INSTALL_PREFIX.
Matching paths in the -rpath-link are not transformed.
The cross-prefix usr-move workaround is assumed not to require extension
regarding CMAKE_STAGING_PREFIX. The staging area is a single prefix, so
there is no scope for cross-prefix symlinks. The CMAKE_INSTALL_PREFIX
is still used to determine the workaround path, and that variable
remains the relevant one even if CMAKE_STAGING_PREFIX is used. If the
generated export files are deployed to the target, the workaround
will still be in place, and still be employed if required.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use definition lists instead of a preformatted block to enumerate
the genex documentation.
Consistently capitalize the description.
Use ``...`` to format genex parameters in the description.
Turn references to commands into links.
Add high level documentation about the motivation for generator
expressions.
Regroup expressions into subsections for different genex types. Add
a high-level description and example of the expressions in each
section.
Explode the documentation for filesystem artifacts, instead of only
referring to the variations.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
a02f3d2 Add policy CMP0040 to disallow custom commands on missing targets
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
c6f339c Add FindBacktrace.cmake module.
|