| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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: !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: !3898
|
| | |/
| |/| |
|
|\ \ \
| | | |
| | | |
| | | | |
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
|
|\ \ \
| | |/
| |/|
| | | |
Merge-request: !3895
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since commit b80557c7bd (file(GENERATE): Evaluate early to allow
generating source files, 2014-11-04, v3.2.0-rc1~398^2) we create the
`cmSourceFile` instances marked with a `GENERATED` source file property
before tracing source dependencies. Move it to even earlier so that
steps in `cmGlobalGenerator::AddAutomaticSources` can operate on all
sources. This also avoids the accidental `O(n^2)` calls for `n` local
generators that we had previously.
This is also needed since commit 83c1657ff7 (Unity build: Generate
sources during Compute step, 2019-10-03) to support `file(GENERATE)`
outputs as sources in a target with `UNITY_BUILD` enabled.
|
|\ \
| | |
| | |
| | | |
Merge-request: !3894
|
| |/
| |
| |
| |
| |
| |
| |
| | |
The same is done for the C and CXX language. This initializes
compiler flags like the sysroot path or deployment target.
Closes: #19794
Suggested-by: Kyle Fleming
|
| | |
|
|/
|
|
|
| |
Release versions do not have the development topic section of
the CMake Release Notes index page.
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
ffa1c76ba3 Help: Add missing 3.16 release notes for CPack/DEB descriptions
a933d8d84e Help: Organize and revise 3.16 release notes
9c9a6e6023 Help: Consolidate 3.16 release notes
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3889
|
| |
| |
| |
| |
| |
| |
| | |
Add notes for the changes from commit 33c7ea513d (CPackDeb: Use
`CPACK_PACKAGE_DESCRIPTION_FILE`, 2019-07-11).
Suggested-by: Alex Turbov <i.zaufi@gmail.com>
|
| |
| |
| |
| |
| |
| | |
Add section headers similar to the 3.15 release notes and move each
individual bullet into an appropriate section. Revise a few bullets.
Drop bullets covering internal interfaces.
|
| |
| |
| |
| |
| | |
Run the `Utilities/Release/consolidate-relnotes.bash` script to move
notes from `Help/release/dev/*` into `Help/release/3.16.rst`.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
c6f08a2125 Help: Clarify how target names are handled in custom commands/targets
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3891
|
| | |
| | |
| | | |
Fixes: #19771
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
3ded5b6da8 install,export: Fix export of a genex following $<INSTALL_PREFIX>
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3886
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The relative path check added by commit 5838aba1aa (Export: Report error
on relative include with genex., 2013-11-26, v3.0.0-rc1~285^2) was added
one condition too early. If the value starts in `${_IMPORT_PREFIX}`
(which comes from `$<INSTALL_PREFIX>`) then it is an absolute path.
Fixes: #19791
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
9c9e66289a Tests: Enable ConfigSources test on every configuration
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3888
|
| | |_|/
| |/| |
| | | |
| | | |
| | | | |
Revise the test itself to work in all configurations and verify that
certain sources are only built by whatever configuration is tested.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
12368e6d15 Help: Document install/strip targets for Ninja/UNIX Makefiles generators
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3887
|
| | |/ /
| |/| | |
|
| | | | |
|
| |_|/
|/| | |
|
| |/
|/| |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
83c1657ff7 Unity build: Generate sources during Compute step
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3884
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The unity build sources need to be added for all generators. Create
them during `cmGlobalGenerator::Compute` to avoid duplicating the calls
in every generator. We already handle Qt autogen there too.
Issue: #19789
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
38c1f2ab22 PCH: Fix CMake test files indentation
1144a4fa47 PCH: Add multi-language PCH generation support
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3885
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If the target has C files, it will get a C PCH file.
The same for C++ files. The linker language is no
longer used to determine which language to use for
PCH.
Fixes: #19790
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | | |
bc4f8f4472 PCH: Use clang's own pch functionality instead of the GCC emulation
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3881
|
| | | |
| | | |
| | | |
| | | | |
Fixes: #19786
|
| |/ /
|/| | |
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
e9500271a3 Help: Add documentation for CTest hardware allocation
d1f100a415 CTest: Add Json output for PROCESSES property
b741ee820d Tests: Add test for CTest hardware allocation feature
3c8a5aad46 Tests: Write tests for cthwalloc helper tool
2d74e54661 Tests: Write cthwalloc helper tool
e34de0691b CTest: Allocate hardware to tests
aee0964851 CTest: Add bin-packing algorithm
c494b2973a CTest: Add cmCTestHardwareAllocator class
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3858
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This helper tool is sufficiently complex that it warrants having its
own test suite.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This algorithm is used to determine whether or not a test can
execute with the available resources. It uses a recursive largest-
first algorithm to try to place the tests into their respective
slots.
|
| | | |
|
| | | |
|
| | | |
|