| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Explain how to use $<BUILD_INTERFACE> and $<INSTALL_INTERFACE> directly
in the documentation of the target_include_directories command and
INTERFACE_INCLUDE_DIRECTORIES target property. Otherwise readers need
to notice the link to the cmake-buildsystem(7) manual and find the
example in that to understand the need for these expressions.
Also fix the explanation in cmake-buildsystem(7) to not claim that
relative paths may be used inside a BUILD_INTERFACE expression.
|
| |
|
|
|
|
|
|
| |
This option was removed during conversion to the reStructuredText
documentation. Restore it. Process documentation starting at
Help/index.rst so that all manuals are included in the output.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These policies are triggered by the use of a particular compiler rather
than outdated CMake code in a project. Avoid warning in every project
that enables a language by not displaying the policy warning by default.
Add variable CMAKE_POLICY_WARNING_CMP<NNNN> to control the warning
explicitly; otherwise enable the warning with --debug-output or --trace.
This breaks with strict policy convention because it does not provide
developers with any warning about the behavior change by default.
Existing projects will continue to build without a warning or change in
behavior. When a developer changes the minimum required version of
CMake in a project to a sufficiently high value (3.0), the project will
suddenly get the new compiler id and may break, but at least the
breakage comes with a change to the project rather than the version of
CMake used to build it.
Breaking strict policy convention is worthwhile in this case because
very few projects will be affected by the behavior change but every
project would have to see the warning if it were enabled by default.
|
| |
| |
| |
| |
| |
| | |
Add inline reST markup as appropriate. Word CMP0047 docs more like
those of CMP0025. State explicitly that the policies must be set
before the project or enable_language command calls.
|
|/
|
|
| |
Do -> To.
|
|
|
|
|
|
|
| |
Restore support for the undocumented <CONFIG>_LOCATION target property
removed by commit v3.0.0-rc1~175^2 (cmTarget: Remove support for
<CONFIG>_LOCATION property, 2013-12-30) as part of the CMP0026 OLD
behavior.
|
|\ |
|
| | |
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| | |
Recently used cmake-gui locations are searched only on Windows because
the Windows registry is used to record the values. This behavior is
historical and may be removed by a policy in the future so rather than
implementing it on other platforms simply document the current behavior.
|
|\ \ |
|
| |/ |
|
|\ \ |
|
| |/
| |
| |
| |
| |
| | |
This command does not support generator expressions. The documentation
was mistakenly extended to claim it in commit v3.0.0-rc1~60^2~3 (Help: Mark
up the buildsystem commands documentation, 2014-02-03).
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Teach the install(FILES) and install(PROGRAMS) commands to evaluate
generator expressions in the list of files.
Extend the ExportImport test to cover installation cases involving
generator expressions.
|
| | | |
| | | |
| | | |
| | | | |
Add inline markup and explicit markup blocks as appropriate.
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
Favor the add_test(NAME) signature and document the limitations of
the plain signature.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Historically CMake used three version components for the feature level.
We released new features while incrementing only the third version
component. Since commit v2.8.2~105^2~4 (New version scheme to support
branchy workflow, 2010-04-23) we used the fourth version component for
bug-fix releases and the development date:
<major>.<minor>.<patch>[.<tweak>][-rc<n>] = Release
<major>.<minor>.<patch>.<date>[-<id>] = Development
This solidified use of three components for the feature level, and was
necessary to continue releasing 2.x versions because:
* Some existing projects performed floating-point comparisons of
${CMAKE_MAJOR_VERSION}.${CMAKE_MINOR_VERSION} to 2.x numbers
so ``x`` could never be higher than 9.
* Version 2.9.<date> was used briefly in post-2.8.0 development in
CVS prior to the transition to Git, so using it in releases may
have caused confusion.
Now that we are moving to 3.x versions, these two restrictions go away.
Therefore we now change to use only two components for the feature
level and use the scheme:
<major>.<minor>.<patch>[-rc<n>] = Release
<major>.<minor>.<date>[-<id>] = Development
|
|/ /
| |
| |
| |
| | |
Release versions do not have the development topic section of
the CMake Release Notes index page.
|
| |
| |
| |
| |
| | |
Bug-fix releases 3.0.x may have their own notes so this will look more
consistent.
|
|/ |
|
|\
| |
| |
| |
| | |
0c54b775 Help: Document the purpose of usage requirements clearly.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
People will be tempted to put things there for convenience, thereby
causing conflicts similar to
http://thread.gmane.org/gmane.comp.compilers.clang.devel/35162/focus=35169
where it is conceivable that the LLVM developers could put a flag on
a target for convenience, which would cause conflicts for some downstreams.
|
|\ \
| | |
| | |
| | |
| | | |
17485e37 FindBoost: Add suport for custom namespaces
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When building boost with an alternate namespace the libraries generated
will have a different naming convention. This is often done to ensure
no symbol conflicts with external libraries built against a different
version of boost. If the namespace used is "myprivateboost::" instead
of "boost::" then the libraries built will be named myprivateboost_foo
instead of boost_foo. Add an option to specify a custom namespace used
to alter the library names that get searched for.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
bf012e0c Help: Format find_package() command documentation
bd6887e4 Help: Document the package registry in cmake-packages.7
|
| | |
| | |
| | |
| | |
| | | |
Add inline markup and explicit markup block syntax as needed.
Add cross-references to other documentation as appropriate.
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Port documentation from the CMake Wiki page at:
http://www.cmake.org/Wiki/CMake/Tutorials/Package_Registry
as of 2014-02-17 into our main documentation.
|
|/
|
|
| |
binary_find -> binary_search.
|
|
|
|
| |
Add CMP0050 to control this behavior.
|
| |
|
|
|
|
|
|
|
| |
Manually read through version control history since the 2.8.12.2
release and write release notes for important user-facing changes.
Co-Author: Stephen Kelly <steveire@gmail.com>
|
|\
| |
| |
| |
| | |
aab11bca Help: Change version 3.0.0 -> 3.0 in policy docs
|
| |
| |
| |
| |
| |
| | |
Starting with 3.0 we will use only two components for the feature level,
and policies are only ever introduced with a bump to the feature level
version.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
0b3e98d9 Help: Don't list debuggable properties in cmake-buildsystem manual.
39d08b92 Help: Add additional hyperlink targets
ef17e293 Help: Document SYSTEM treatment of IMPORTED target INTERFACE_INCLUDE_DIRS
|
| | | |
|
| | | |
|
| |/
| |
| |
| | |
Document how the behavior can be controlled.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
4b7f2f52 Help: Add hyperlink targets for argument types in cmake-language(7)
113df227 Remove ChangeLog.manual
79f55909 Remove ChangeLog.txt
d25dbc90 Tests/BundleTest: Drop use of ChangeLog.txt
|
| |/
| |
| |
| |
| | |
Add reStructuredText hyperlink targets for the bracket, quoted, and
unquoted argument sections.
|
|/
|
|
| |
'to not to' -> 'not to'
|
|
|
|
| |
Link to the cmake-qt manual.
|