Martin Willers authored 3 years ago and Brad King committed 3 years ago

Based on the implementation in Terminal.c:kwsysTerminalStreamIsVT100.

Amine Najahi authored 3 years ago and Brad King committed 3 years ago

Fixes: #21792

NMake version 9 and above support UTF-8 encoded makefiles with a BOM.

Run `nmake -?` and extract the version from its output.
Use a timeout because Watcom tools come with a `nmake` tool
that always waits for user input on `-?`.

Fix a typo from commit 940fc629 (macOS: Respect OSX_ARCHITECTURES for
ASM, 2020-08-21, v3.19.0-rc1~270^2).

Fixes: #22152

Fixes: #19712

Issue: #19712

Kinan Mahdi authored 3 years ago and Brad King committed 3 years ago

Fixes: #22104

Fixes: #22108

Fixes: #22123

In v3 of the presets, the `--toolchain` command line argument now
has a preset mapping.

Fixes: #20553

Tell `MSBuild` to use the same `Platform` that we generate into the
`VCTargetsPath` detection project.

Fixes: #22068

Lingkai Dong authored 3 years ago and Brad King committed 3 years ago

The compile options `--march=<arch>` and `--mcpu=<cpu>` and the
link option `--cpu=<cpu>` are automatically added by CMake based
on `CMAKE_SYSTEM_PROCESSOR` or `CMAKE_SYSTEM_ARCH`. But this is not
sufficient, because armclang also supports enabling or disabling
features using `+<feature>`:

    -mcpu=<name>[+[no]<feature>+...]

For example:

    -mcpu=cortex-a57+nocrypto+nofp+nosimd+crc

(Reference: https://developer.arm.com/documentation/dui0774/k/Compiler-Command-line-Options/-mcpu?lang=en)

The problem is, even if a project adds a flag with features it needs,
CMake still adds flags, resulting in code that is compiled with wrong
CPU features and unable to run.

Add policy `CMP0123` to not automatically add compile or link options,
and let projects set them instead.

Co-Author: Brad King <brad.king@kitware.com>
Fixes: #21173

Orgad Shaneh authored 3 years ago and Brad King committed 3 years ago

Detect MSYS as CYGWIN, with the required adaptations.

Addresses #18654

Consider the case where the find_package call for QtCore is wrapped in a
function call. Then AutoGen cannot determine the Qt version, because it
only looks at variables and directory properties. The former don't leave
the function scope and the latter are not set by default.

As a fallback, locate the moc executable via its target and call it with
the --version argument to determine the Qt version.

Issue: #22028