| commit | 2f5276089c50cc76bc9282ec1246304c4dafc5b8 | [log] [tgz] |
|---|---|---|
| author | Charles Nicholson <nicholsonc@google.com> | Thu Sep 05 17:06:11 2019 -0400 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Sep 05 21:31:37 2019 +0000 |
| tree | e9d6b730bbaeff56b71ec1e636019147556a8935 | |
| parent | fc2f07a866d3089965a6a034bb1112d5c44601d7 [diff] |
[cleanup] Remove stale documentation from get_target_outputs. The if statement starting at line 122 in the left-side diff rejects binary targets. This CL simply updates the documentation to reflect that current reality. Change-Id: I745c4c8f894c8c6c7d2d85e57b981ff0d598777b Reviewed-on: https://gn-review.googlesource.com/c/gn/+/5960 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.
Related resources:
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.
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.