|author||Dirk Pranke <email@example.com>||Wed Apr 03 09:05:09 2019 -0700|
|committer||Commit Bot <firstname.lastname@example.org>||Wed Apr 03 16:39:36 2019 +0000|
Remove dpranke from OWNERS. I'm no longer tracking the work in this repo closely enough, nor am I writing enough C++, to really be a good owner at this point. Perhaps this will change again at some point in the future, but for now, considering me an OWNER just seems like it can confuse people. Change-Id: I2224027f204c7c61ce71a7e62f0baf335f84b4f9 Reviewed-on: https://gn-review.googlesource.com/c/gn/+/4500 Reviewed-by: Brett Wilson <email@example.com> Commit-Queue: 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.