|author||Nate Fischer <email@example.com>||Tue Jan 08 17:32:01 2019 -0800|
|committer||Commit Bot <firstname.lastname@example.org>||Wed Jan 09 18:14:37 2019 +0000|
Docs: regenerate docs This only regenerates documentation to reflect changes since the last docs generation, no change to content otherwise. This should be non-controversial, since this mostly addition. Test: out/gn help --markdown all > docs/reference.md Change-Id: I0c0777947f0b320246badf7e5c302282df765a16 Reviewed-on: https://gn-review.googlesource.com/c/3680 Reviewed-by: Scott Graham <email@example.com> Commit-Queue: Scott Graham <firstname.lastname@example.org>
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
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 w/ GN‘s development on Chromium’s gn-dev@ Google Group.