commit | 8dc294d0f168971d6df6fb547573eaf631507081 | [log] [tgz] |
---|---|---|
author | Petr Hosek <phosek@google.com> | Mon Aug 12 17:10:48 2019 -0700 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Aug 13 03:16:47 2019 +0000 |
tree | 79771fdbc5b140cd260b657502f8b794a1f7047c | |
parent | 21242330c05d1747cc03f6398b7a76ef646cba2d [diff] |
Write Rust deps even if there are only non-Rust ones When Rust target has only non-rust dependencies, currently we would avoid writing depencencies altogether which is not correct. Change-Id: I6c86de8a8a23831a4126e4c46c05fdefe7de2916 Reviewed-on: https://gn-review.googlesource.com/c/gn/+/5860 Reviewed-by: Brett Wilson <brettw@google.com> Commit-Queue: Petr Hosek <phosek@google.com>
GN is a meta-build system that generates build files for Ninja. There is documentation in docs/ and a presentation on it.
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.