| commit | 0790d3043387c762a6bacb1ae0a9ebe883188ab2 | [log] [tgz] |
|---|---|---|
| author | Nico Weber <thakis@chromium.org> | Mon Nov 19 18:51:56 2018 -0500 |
| committer | Commit Bot <commit-bot@chromium.org> | Mon Nov 19 23:57:46 2018 +0000 |
| tree | 92c72c3ef726dfe9baadda2ea3db26ab3b093491 | |
| parent | 9dfbe7fd95a27787bc63094e2e00677c31d506d0 [diff] |
List .gn file in build.ninja.d. This way, gn reruns when the .gn file is touched. Bug: 24 Change-Id: Iabc21ee5f4b82106c7d8004f8372b3d83471b515 Reviewed-on: https://gn-review.googlesource.com/c/3321 Commit-Queue: Brett Wilson <brettw@chromium.org> Reviewed-by: Brett Wilson <brettw@chromium.org>
GN is a meta-build system that generates build files for Ninja. There is documentation in docs/.
You can download the latest version of GN binary for Linux, macOS and Windows.
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 cl.exe, link.exe, and 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 CC, CXX, and AR.
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.