|author||Julie Hockett <email@example.com>||Tue Apr 02 14:41:52 2019 -0700|
|committer||Commit Bot <firstname.lastname@example.org>||Mon Apr 22 19:04:25 2019 +0000|
Move Tool logic out of Toolchain This sets up the ability for tools to self-manage and dispatch, and replaces the ToolType enum with the more dynamic tool name constant. This is part of the Tool refactoring to allow for additional sets of tools to be added, enabling support for new languages to be added. Same as in the previous patch, this unfortunately requires touching a bunch of files since the enum is prevalent. Change-Id: Ia9eebb2525749aa0c525f85a9d89ce9ca6ca0159 Reviewed-on: https://gn-review.googlesource.com/c/gn/+/4462 Commit-Queue: Julie Hockett <email@example.com> Reviewed-by: Brett Wilson <firstname.lastname@example.org>
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
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
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 w/ GN‘s development on Chromium’s gn-dev@ Google Group.