| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Use the TortoiseHg registry entry as a search path.
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
f6cae4ea Tests: Remove some trailing black lines.
c0ea4c5c Makefile: Fix comment indentation.
5e0c73c7 cmGlobalGenerator: Remove unused variable.
907c09cd include_directory: Add missing include.
a74d125a Help: Fix typo
317d8498 Small typo fix
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The cmGeneratorExpression is used here, but the header for it is not
in the include heirarchy. This would be a compile error if the file
were compiled as a standalone translation unit, but it is instead
used in a mini-unity-build by inclusion in cmCommands.cxx. The header
for cmGeneratorExpression happens to be included first, so the
compilation works fine.
IDEs do not know this however, and flag the use as an error.
|
| | | |
| | | |
| | | |
| | | | |
binary_find -> binary_search.
|
| | | | |
|
| |_|/
|/| | |
|
| |/
|/| |
|
|\ \
| | |
| | |
| | |
| | | |
7b1f966a Windows: Make file delete/rename retry configurable
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Several CMake operations need to replace files in rapid succession.
This commonly fails on Windows due to filesystem lock behavior so
we have retry loops. No matter how many times we retry or how long
we delay there will inevitably be someone with an environment that
needs more. Make the retry count and delay configurable in the
Windows Registry keys:
{HKCU,HKLM}/Software/Kitware/CMake/Config
in DWORD values
FilesystemRetryCount = Number of tries
FilesystemRetryDelay = Delay in milliseconds between tries
Leave the feature undocumented for now to see how it goes.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
9db9c1fc cmTarget: Don't try to get sources of an INTERFACE_LIBRARY.
|
| | | |
| | | |
| | | |
| | | | |
An an assert to ensure this.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
9d35f7c4 cmake-mode.el: Add help for variables/properties/complete. Factorize.
7cc21e9a cmake-mode.el: Add the ability to retrieve module help.
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
22e5c6c2 Kate: handle spaces in build dir
|
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
They need to be escaped in the json file... I'm quite
sure I tested this before, obviously I didn't test it
correctly.
Alex
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
cab5ebd4 Intel compiler: add -isystem flag under Linux
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This makes the SYSTEM keyword work with the Intel compiler
under Linux. AFAIK this is supported neither under Windows nor OSX.
Alex
|
| |/ / / /
|/| | | | |
|
| | | | | |
|
| | | | | |
|
| |_|/ /
|/| | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
26762e16 Ninja: Cache target-level flags
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
Instead of figuring out target flags per-source file, cache the flags
that are being used. This results in a *much* faster generate time for
Ninja.
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
77b2e6f1 OS X: Escape path given to -isysroot flag
|
| |/ /
| | |
| | |
| | |
| | | |
Ensure that paths containing spaces or other special characters are
escaped correctly on the command line.
|