|author||Wink Saville <firstname.lastname@example.org>||Fri Nov 08 12:15:00 2019 -0800|
|committer||Commit Bot <email@example.com>||Fri Nov 08 22:14:20 2019 +0000|
Change args.gn to reference `gn help buildargs` Executing `gn buildargs` is an error: $ gn buildargs ERROR Command "buildargs" unknown. Change-Id: I53d9d50b1ca967bb26e673d1317246a73f2fb85d Reviewed-on: https://gn-review.googlesource.com/c/gn/+/6520 Reviewed-by: Haowei Wu <firstname.lastname@example.org> Reviewed-by: Brett Wilson <email@example.com> Commit-Queue: Brett Wilson <firstname.lastname@example.org>
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.
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 cl upload --gerrit
When revising a change, use:
git commit --amend git cl upload --gerrit
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.