Call for 1.11 testing: Validation Nodes, UTF-8 on Windows, missingdeps and inputs tool, ...

[jha...@gmail.com]

Hi everyone,

we'd like to release 1.11 from current master.

This release adds Validation Nodes which are a new way to add jobs like linters or static analyzers to the build graph. They are added using |@ and don't produce any outputs. You can read more about the motivation and the syntax here: https://github.com/ninja-build/ninja/pull/1800

Another big change is that Ninja now uses UTF-8 on Windows. This means that while previous versions of Ninja used the local ANSI encoding it will now always use UTF-8 allowing filenames and output with special characters. For this to work you'll need Windows 10 Version 1903 or newer. And for the console output to show Unicode characters you'll need to set the codepage to 65001. More information at: https://github.com/ninja-build/ninja/pull/1915

Note that this is a breaking change if you relied on non-ASCII characters of the local codepage! If you want to query Ninja what codepage it uses in your generator, call `ninja -t wincodepage` and act accordingly.

There are also two new tools:

missingdeps: https://github.com/ninja-build/ninja/pull/1331

inputs: https://github.com/ninja-build/ninja/pull/1730

And as it was often requested, ninja now has a --quiet flag :)

For a complete list of changes see https://github.com/ninja-build/ninja/milestone/3?closed=1

Please test a build of the master branch with your projects and report any problems. Thanks!

[Brad King]

On Sat, Apr 30, 2022 at 5:30 AM wrote:
> Please test a build of the master branch with your projects

CMake's nightly CI pipeline regularly runs our test suite
on Linux, macOS, and Windows using a Ninja built from
the upstream repository's default branch. It is currently
happy with Ninja's `master` branch.

-Brad