| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
If a package is requested with an EXACT version, that doesn't imply
that dependencies must be found EXACTly too.
Extend the macro to allow specifying that a dependency must be found
by EXACT version instead.
|
|\ \ |
|
| |/
| |
| |
| |
| |
| | |
Commit v3.0.0-rc1~71^2~9 (Qt4: Use IMPORTED executable names with
custom commands., 2014-01-24) erroneusly changed this command to
use the wrong target.
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Python 3.4.0rnc1 was released on 2014-02-20.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Drop unnecessary NO_POLICY_SCOPE options. Document why the remaining
options are necessary.
|
| |/ /
| | |
| | |
| | |
| | | |
Policies CMP0027, CMP0038, and CMP0046 have per-target meaning so
record the policy settings on targets as they are created.
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | | |
This internal option requires two arguments, not just one. Fix the
argument count required to recognize the option.
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
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).
|
|\ \ \
| |_|/
|/| | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
The most significant change since Ruby 1.9 is the changed path of
config.h, from RbConfig::CONFIG['rubyhdrdir'] to
RbConfig::CONFIG['rubyarchhdrdir'].
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
This matches the other macro variables.
|
| | | |
| | | |
| | | |
| | | | |
The code set cmake_fd_version, but used ${version}.
|
|\ \ \ \ |
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
My last related commit e5e3f3d4 (CTest: filter /showIncludes output from
ninja compile launcher, 2013-12-01) filtered /showIncludes messages from
the generated xml output but they also need to be filtered in
ScrapeLog(). Otherwise they are being detected as warnings when using
compilers withs english diagnostics.
|
|\ \ \ \ \
| | |/ / /
| |/| | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The ARGV1 value could come from a wrapping context if find_dependency
is called from a function.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Avoid setting a variable called 'version' etc.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If there is no ARGV1, that is fine; version will be made empty, and no
version will be passed to find_package().
This is relevant when find_dependency is invoked multiple times,
sometimes with a version specified and sometimes without.
find_dependency(dep1 3.4)
find_dependency(dep2) # version still set to 3.4.
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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 a Makefile member to the cmInstallFilesGenerator class and
populate it on construction. This will be useful in a following
change to evaluate generator expressions with proper context.
|
| | |/ / /
| |/| | |
| | | | |
| | | | | |
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.
|
|\ \
| | |
| | |
| | |
| | | |
e346c47a FindOpenSSL: Prefer OPENSSL_ROOT_DIR first (#14764)
|
| |/
| |
| |
| |
| | |
Use hints computed from this explicit variable before those
computed by PkgConfig. They are more specific.
|
|\ \
| | |
| | |
| | |
| | | |
ac2527e1 FindJNI: Add ppc64le architecture
|
| | |
| | |
| | |
| | | |
Signed-off-by: Dinar Valeev <dvaleev@suse.com>
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
17485e37 FindBoost: Add suport for custom namespaces
|