commit | 4e97d9be7a38baa8a4dc5d196173f73774c4180c | [log] [tgz] |
---|---|---|
author | Scott Graham <scottmg@chromium.org> | Wed Jan 29 17:07:24 2020 -0800 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Jan 30 13:07:08 2020 +0000 |
tree | 72d01fdfe2f5d528879b727eda3e1ecc4a0aad5c | |
parent | 12f53f06554d665c82160d4edeab0200a37081f8 [diff] |
vim: Fix invalid import in gn-format.py Broken at 12f53f06554d665c82160d4edeab0200a37081f8. I swear I tried this, but I must have confused myself by not re-source'ing something. (from __future__ imports have to go at the top of the file before other imports.) Change-Id: I23c56ca7a21dbf83469e92834828ea4557dd6696 Reviewed-on: https://gn-review.googlesource.com/c/gn/+/7260 Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by: Nico Weber <thakis@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.