| commit | d2f5e438ddcf6d51ba47aa71909a1bca9a1555f0 | [log] [tgz] |
|---|---|---|
| author | P.Y. Laligand <pylaligand@google.com> | Thu May 21 20:03:17 2020 +0000 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed May 27 22:03:37 2020 +0000 |
| tree | 8652c1ff96c707f9264881396b933b4dc1404293 | |
| parent | 7d9b8111a2e0c31c429a064f0480f16bb8b51e0f [diff] |
Add new build configuration variable to add an extension to build file names. Using such an extension would result in a name of the form "BUILD.$extension.gn". This is useful notably for code that is expected to get built in two different GN builds. Change-Id: I1a8fce9ded95d1300d0bf2a23e983301acb9f9d7 Reviewed-on: https://gn-review.googlesource.com/c/gn/+/8500 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.
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.
To build and run the simple example with the default gcc compiler:
cd examples/simple_build ../../out/gn gen -C out ninja -C out ./out/hello
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 push origin HEAD:refs/for/master
The first time you do this you'll get an error from the server about a missing change-ID. Follow the directions in the error message to install the change-ID hook and run git commit --amend to apply the hook to the current commit.
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.
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.