|author||RJ Ascani <firstname.lastname@example.org>||Wed Sep 16 10:34:35 2020 -0700|
|committer||Commit Bot <email@example.com>||Wed Oct 07 17:20:54 2020 +0000|
Switch remaining stamp targets to phony targets GN uses stamp files for a variety of output types as a mechanism for completing a group of dependencies. Ninja's phony targets can be used in a similar manner. The GN 'group', 'generated_file', 'bundle_data', 'copy', 'action', 'action_for_each' and 'create_bundle' output types each generate a stamp file as an output for other targets to depend on. This CL replaces those stamp targets with a phony alias target. For a few target types, GN optionally creates a "<target>.inputdeps" and/or "<target>.input" stamp files to represent a group of input dependencies or inputs, respectively. This is useful for limiting the size of ninja files because the dependencies only have to be listed once. As with the stamp files generated for the aforementioned output types, this CL also replaces those stamp targets with a phony alias target. Finally, there are several intermediate stamp files that are created for certain outputs, such as the code signing stamp for `create_bundle` targets. Where possible, these are also replaced with phony alias targets. Bug: 186, 188, 191, 194 Change-Id: I5b257147affc55bb8b093a3f39c7e9a5b56b6f6c Reviewed-on: https://gn-review.googlesource.com/c/gn/+/10100 Commit-Queue: Brett Wilson <firstname.lastname@example.org> Reviewed-by: Brett Wilson <email@example.com>
GN is a meta-build system that generates build files for Ninja.
Alternatively, you can build GN from source:
git clone https://gn.googlesource.com/gn cd gn python build/gen.py ninja -C out # To run tests: out/gn_unittests
On Windows, it is expected that
lib.exe can be found in
PATH, so you'll want to run from a Visual Studio command prompt, or similar.
On Linux and Mac, the default compiler is
clang++, a recent version is expected to be found in
PATH. This can be overridden by setting
There is a simple example in examples/simple_build directory that is a good place to get started with the minimal configuration.
To build and run the simple example with the default gcc compiler:
cd examples/simple_build ../../out/gn gen -C out ninja -C out ./out/hello
For a maximal configuration see the Chromium setup:
and the Fuchsia setup:
If you find a bug, you can see if it is known or report it in the bug database.
GN uses Gerrit for code review. The short version of how to patch is:
Register at https://gn-review.googlesource.com. ... edit code ... ninja -C out && out/gn_unittests
Then, to upload a change for review:
git commit git push origin HEAD:refs/for/master
The first time you do this you'll get an error from the server about a missing change-ID. Follow the directions in the error message to install the change-ID hook and run
git commit --amend to apply the hook to the current commit.
When revising a change, use:
git commit --amend git push origin HEAD:refs/for/master
which will add the new changes to the existing code review, rather than creating a new one.
We ask that all contributors sign Google's Contributor License Agreement (either individual or corporate as appropriate, select ‘any other Google project’).
You may ask questions and follow along with GN‘s development on Chromium’s gn-dev@ Google Group.