| commit | 796ed47bbdc5eb9889476c6bf380cf8ca51ea192 | [log] [tgz] |
|---|---|---|
| author | Brett Wilson <brettw@chromium.org> | Mon Jul 16 15:11:09 2018 -0700 |
| committer | Commit Bot <commit-bot@chromium.org> | Mon Jul 16 22:18:41 2018 +0000 |
| tree | 8bafb3b1c1a3d4fa01f8efa20553889eddadc224 | |
| parent | 63b72701a5056460fe81f2e7937c24aded929501 [diff] |
Add reference.md This was generated by running "gn help --markdown all" Change-Id: I7641e7c91ecc57eab782b7eab69444aa5787b679 Reviewed-on: https://gn-review.googlesource.com/2220 Reviewed-by: Brett Wilson <brettw@chromium.org> Commit-Queue: Brett Wilson <brettw@chromium.org>
GN is a meta-build system that generates build files for Ninja.
git clone https://gn.googlesource.com/gn cd gn python build/gen.py ninja -C out
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.
GN uses Gerrit for code review. The short version of how to patch is:
... edit code ... ninja -C out && out/gn_unittests
Then, to upload a change for review:
git commit git push origin HEAD:refs/for/master # This uploads for review.
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.
TODO: AUTHORS, CLA, etc.