1529f4a9 Utilities/Release: Teach "push" script to create destination subdirectory
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3902

Extend the script added by commit 9bf97363 (Utilities/Release: Replace
upload step with a "push" script, 2019-05-24, v3.15.0-rc1~56^2) to
create the destination subdirectory for the CMake version being pushed.

d00bb419 Add deprecation warnings for policies CMP0069 and below
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3893

The OLD behaviors of all policies are deprecated, but only by
documentation.  Add an explicit deprecation diagnostic for policies
introduced in CMake 3.9 and below to encourage projects to port away
from setting policies to OLD.

5d3b825c ExternalProject: fix some documentation typos
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3898

7bbddeb7 CLI: Rename --loglevel to --log-level for naming consistency
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Alex Turbov <i.zaufi@gmail.com>
Merge-request: !3899

36ded610 PCH: Generate sources during Compute step
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3890

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

Merge-request: !3895

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

f1fb63b3 file(GENERATE): Create output file structures even earlier
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3895

638fa412 Apple: Set Clang ASM compiler features
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3894

9df56ece Merge branch 'backport-vs-16.4-global-targets'
ac1a1bf1 VS: Tell VS 16.4 not to verify CMake-provided custom command outputs
04e5f30a VS: Tell VS 16.4 not to verify CMake-provided custom command outputs
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3896

Merge-request: !3896

Merge-request: !3896

Extend the fix from commit 0578239d (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

Extend the fix from commit 0578239d (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

Merge-request: !3894

Since commit b80557c7 (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 83c1657f (Unity build: Generate
sources during Compute step, 2019-10-03) to support `file(GENERATE)`
outputs as sources in a target with `UNITY_BUILD` enabled.

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