| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Match this message:
Could not resolve host: -no-site-; Name or service not known
^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|\ \ |
|
| |/ |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Implementation indicates that at least two components of VERSION must
be specified (see Source/cmCMakeMinimumRequired.cxx.) Therefore the
minor version is not optional.
|
| |/
| |
| |
| |
| |
| | |
The COMPATIBLE_INTERFACE_NUMBER_MAX example now sets
INTERFACE_CONTAINER_SIZE_REQUIRED on lib1Version2 and lib1Version3.
Previously set it on lib1Version2 twice and never on lib1Version3.
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since commit v3.5.0-rc1~32^2~1 (ExternalProject: Simplify `cmake
--build` configuration passing, 2016-01-19) we use the `$<CONFIG>`
generator expression to generate the `cmake --build . --config <config>`
value for the default BUILD_COMMAND instead of the CMAKE_CFG_INTDIR
placeholder value provided by multi-config generators. However, some
projects have been abusing the old implementation detail by setting
CMAKE_CFG_INTDIR themselves to get a specific configuration. Those
projects should be updated to set their own BUILD_COMMAND to get
non-default behavior. Meanwhile we can be compatible with their
existing releases by detecting when CMAKE_CFG_INTDIR is not a
generator-provided placeholder and using its value instead.
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Refactoring in commit v3.5.0-rc1~347^2~2 (Set the current dirs on the
snapshot before creating the cmMakefile) accidentally changed the
source and binary directories configured in `cmake -E cmake_depends`
for use during dependency scanning. This can cause the wrong directory
information to be loaded. It also breaks Fortran module dependency
scanning for modules provided by targets in subdirectories that do
not have Fortran_MODULE_DIRECTORY set.
Fix the dependency scanning directory configuration and add a test to
cover the Fortran module case in which the breakage was observed.
Reported-by: Kelly Thompson <kgt@lanl.gov>
|
| | |
|
|/
|
|
|
| |
Release versions do not have the development topic section of
the CMake Release Notes index page.
|
|\
| |
| |
| |
| |
| | |
ad701d9f Help: Organize and revise 3.5 release notes
377a12b2 Help: Consolidate 3.5 release notes
|
| |
| |
| |
| |
| | |
Add section headers similar to the 3.4 release notes and move each
individual bullet into an appropriate section. Revise a few bullets.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Move all development release notes into a new version-specific document:
tail -q -n +3 Help/release/dev/* > Help/release/3.5.rst
git rm -- Help/release/dev/*
except the sample topic:
git checkout HEAD -- Help/release/dev/0-sample-topic.rst
Reference the new document from the release notes index document.
Add a title and intro sentence to the new document by hand.
|
|\ \
| | |
| | |
| | |
| | | |
ccb2d5c0 cmAlgorithms.h: remove superfluous semicolon after method
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | | |
6ffc4323 cmConditionEvaluator: Fix matching of `CMAKE_MATCH_*` values (#15944)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
While evaluating `if(MATCHES)` we get a `const char*` pointer to the
string to be matched. On code like
if(CMAKE_MATCH_COUNT MATCHES "Y")
the string to be matched may be owned by our own result variables.
We must move the value to our own buffer before clearing them.
Otherwise we risk reading freed storage.
|
| |/
|/| |
|
|\ \
| | |
| | |
| | |
| | | |
6f83db1c Help: Fix typo in `cmake-developer(7)` manual
|
| | |
| | |
| | |
| | | |
Fix spelling mistake `sytem` => `system`.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
fa78ee97 FindGit: Improve documentation formatting
facfb52c FindGit: Document Git_FOUND, unset internal var
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Git is called Git, not git.
* FindGit sets Git_FOUND, too.
* Unset internal variable git_names
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
d257d681 add_custom_command: Clarify error when TARGET is out of scope (#15681)
4d53e0a7 Help: Clarify `add_custom_command(TARGET)` scope (#15681)
8c615af4 Help: Clarify policy `CMP0040` documentation (#15681)
63c5808f Help: Clarify scope of `if(TARGET)` expression
a336e438 Help: Improve markup in `if` command documentation
88968265 Help: Improve markup in `get_target_property` documentation
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The add_custom_command(TARGET) signature only works for targets defined
in the current directory. Clarify this in the error message when the
target exists but was defined elsewhere.
Inspired-by: Bartosz Kosiorek <gang65@poczta.onet.pl>
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
State explicitly that the target must be defined in the current
directory. While at it, improve markup formatting.
|
| | | | | |
|
| | | | | |
|
| | |_|/
| |/| | |
|
| |_|/
|/| | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
|\ \
| |/
|/|
| |
| | |
1053db7b UseJava: Fix documented name of `CLASSDIR` property (#15936)
|
| |
| |
| |
| | |
It is not `CLASS_DIR`.
|
| | |
|
|/ |
|
|\ |
|
| | |
|
|\ \
| |/ |
|
| |\ |
|
|\ \ \
| | |/
| |/|
| | |
| | | |
d7e863c1 VS: Do not fail on Windows 10 with VS 2015 if no SDK is available (#15929)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since commit v3.4.0-rc1~5^2~1 (VS: Add support for selecting the Windows
10 SDK, 2015-09-30) the VS 2015 generator requires a Windows 10 SDK to
be available when CMAKE_SYSTEM_VERSION specifies Windows 10 (e.g. when
building on a Windows 10 host). Howewver, it is possible to install VS
2015 without any Windows 10 SDK. Instead of failing with an error
message about the lack of a Windows 10 SDK, simply tolerate this case
and use the default Windows 8.1 SDK. Since building for Windows Store
still requires the SDK, retain the diagnostic in that case.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
b94e855d FindBoost: Add support for Boost 1.61
|
| | | | |
|