| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
c1435d9812 Help: Fix error in resource allocation example
eb9d945f14 CTest: Rename hardware -> resources for RunCMake tests
c544cb6698 CTest: Rename hardware -> resources for source code
6ce27d3a2e cmCTestMultiProcessHandler: Rename resource locking functions
a7c1e15cc4 CTest: Rename hardware -> resources for CMake variables, command options
73a40b19ff CTest: Rename "Processes" lexer to "ResourceGroups"
af9ed543b0 CTest: Rename PROCESSES test property to RESOURCE_GROUPS
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3994
|
| | |
|
| |
| |
| |
| |
| |
| | |
Renaming these ahead of other refactoring which will use the
previous names. The previous names more accurately reflect their
purpose after this commit anyway (talking about locking and
unlocking rather than allocating and deallocating).
|
| |
| |
| |
| |
| |
| | |
Only changes the user-visible effects of renaming hardware
allocation to resource allocation. Code changes are the minimum
needed to achieve that.
|
| |
| |
| |
| |
| | |
The corresponding test property `PROCESSES` has been renamed to
`RESOURCE_GROUPS`.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The `PROCESSES` test property name added for CMake 3.16 is too close to
the existing `PROCESSORS` test property. Furthermore, the property in
principle specifies groups of resources organized in a way that is
meaningful to a particular test. The groups may often correspond to
processes but they could have other meanings. Since the property name
`PROCESSES` has not been in a final 3.16 release yet, simply rename it
to `RESOURCE_GROUPS`.
Fixes: #19914
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
7ddf462304 Unity build: Include GENERATED files into unity build
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Julien Schueller <schueller@phimeca.com>
Merge-request: !4001
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There is no reason to skip the generated files, in case of problems
one can use the SKIP_UNITY_BUILD_INCLUSION property.
Fixes: #19925
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
f0c00bec1d CMakeVersion.rc: Fix build with llvm-rc
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4003
|
| |/ /
| | |
| | |
| | | |
llvm-rc expects versioning as having four items, it fails otherwise.
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
0ce8a5c08d Xcode: Fix generated references to CMakeLists.txt files
9457c95aa0 cmGlobalXCodeGenerator: Mark known source locations
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3999
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Refactoring in commit 2d888e3390 (cmSourceFile: Rename mutating
GetFullPath() overload, 2019-08-29, v3.16.0-rc1~160^2) accidentally left
the paths to `CMakeLists.txt` files empty in generated Xcode project
files.
Fixes: #19927
|
| |/ |
|
|\ \
| | |
| | |
| | | |
Merge-request: !3979
|
| |/
| |
| |
| | |
Fixes: #19769
|
|\ \
| | |
| | |
| | | |
Merge-request: !3983
|
| |/ |
|
|\ \
| | |
| | |
| | | |
Merge-request: !3985
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | | |
release-3.16
Merge-request: !3968
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Extend the change from commit 1d00ba9ccf (Find: find_package prefers
variable CMAKE_FIND_USE_REGISTRY, 2018-11-13, v3.16.0-rc1~461^2~1)
to cover the system package registry too.
Fixes: #19890
|
|/
|
| |
Fixes: #19909
|
| |
|
|\
| |
| |
| | |
Merge-request: !3962
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On Windows, `CollapseFullPath` called with a path that ends with a dot
might return a file with the same base name but any extension.
To make sure we get only the file with the requested header extension,
pass the complete file name to `CollapseFullPath`.
Fixes: #19892
|
|\ \
| | |
| | | |
Merge-request: !3948
|
| |/
| |
| |
| | |
This fixes two errors: not accounting for the trailing null and a
misunderstanding of what std::numeric_limits::digits10 means.
|
|/ |
|
| |
|
|\
| |
| |
| | |
Merge-request: !3928
|
| |
| |
| |
| |
| |
| |
| |
| | |
Teach the Makefile generator to scan the implicit dependencies of PCH
creation. When a header named by `target_precompile_headers` changes
the corresponding PCH must be rebuilt and all consumers recompiled.
Fixes: #19830
|
| | |
|
|\ \
| | |
| | |
| | | |
Merge-request: !3927
|
| |/
| |
| |
| |
| |
| |
| | |
When generating `IMPORTED_LINK_INTERFACE_LANGUAGES`, do not treat the
entries as target names.
Fixes: #19846
|
|\ \
| | |
| | |
| | | |
Merge-request: !3921
|
| |/
| |
| |
| |
| | |
Ensure that we preserve the `CMAKE_Swift_COMPILER_TARGET` variable to
use cross-compilation for testing the Swift compiler if appropriate.
|
|\ \
| | |
| | |
| | | |
Merge-request: !3912
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since commit 4ca0526f8a (cmake: Pass -S and -B into PreLoad.cmake and -C
scripts, 2019-08-20, v3.16.0-rc1~195^2) the value of `CMAKE_SOURCE_DIR`
is the source directory rather than the current working directory.
This was correct on its own, but the place storing that value is also
used as the base for relative paths specified on the command line.
The latter should of course be relative to the current working
directory.
The fix is to switch to use a full path internally, unless a full path
is already specified. Add tests for the behaviour of `-C` under these
four circumstances:
{with -S, without -S} x {full path, relative path}
Fixes: #19827
|
|\ \
| | |
| | |
| | | |
Merge-request: !3910
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Distro maintainers who are building from Git with patches added on
may want to disable the automatic Git suffixing, as it does not
provide any useful information and simply confuses the end user.
Add an undocumented CMake_VERSION_NO_GIT variable to disable this.
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Update the approach from commit fe2c558ba6 (CMakeVersion: Preserve Git
information during 'git archive', 2019-07-25, v3.16.0-rc1~337^2) to
prefer `export-subst` information. This will allow exported source
trees to be imported into unrelated Git repositories while still using
the original upstream CMake commit information.
|
|\ \
| |/
|/|
| | |
Merge-request: !3908
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
While the flag tables for C and C++ were generated from MSBuild `.xml`
files, the CSharp flag tables were written by hand. Copy the `v141`
flag table to use for the `v142` toolset.
Remove the special case added by commit 626c51f47b (VS: Update for
Visual Studio 2019 Preview 2, 2019-01-24, v3.14.0-rc1~74^2) that mapped
the v142 flag table lookup to v141 since we now have the real v142
table.
Fixes: #19828
|
| | |
|
|\ \
| | |
| | |
| | | |
Merge-request: !3899
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Other multi-word command line options use hyphens to separate
the words, so the --loglevel option introduced in CMake 3.15 was
inconsistent in this regard. Rename it to --log-level but still support
the original --loglevel name to preserve backward compatibility.
|
|\ \ \
| | | |
| | | |
| | | | |
Merge-request: !3890
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Merge-request: !3896
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Extend the fix from commit 0578239d3a (VS: Tell VS 16.4 not to verify
SYMBOLIC custom command outputs, 2019-09-23, v3.15.4~2^2) to apply to
outputs in CMake-provided targets like `install`. Simply mark these
outputs as `SYMBOLIC` too since they are not actually generated.
Fixes: #19737
|