| commit | 387e3ab4a6ccf1c8879c4fa91b7f785a92d7d137 | [log] [tgz] |
|---|---|---|
| author | Dirk Pranke <dpranke@chromium.org> | Mon Jul 23 14:15:15 2018 -0700 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Aug 01 19:56:11 2018 +0000 |
| tree | fce46cd124201d8b78676d00c5052697611178f3 | |
| parent | 11e09914b1a4cd7b6f902e2f76798c47e9312e8e [diff] |
Add an OWNERS file. This adds a top-level OWNERS file. I don't think any tooling will enforce OWNERS checks at this point, so this is mostly for documentary purposes. Change-Id: Ifb7a9dd40ff3a4805a85d86075aa93fb808d2d31 Reviewed-on: https://gn-review.googlesource.com/2381 Commit-Queue: Dirk Pranke <dpranke@google.com> Commit-Queue: Brett Wilson <brettw@chromium.org> Reviewed-by: Petr Hosek <phosek@google.com> Reviewed-by: Brett Wilson <brettw@chromium.org>
GN is a meta-build system that generates build files for Ninja.
git clone https://gn.googlesource.com/gn cd gn python build/gen.py ninja -C out
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.
GN uses Gerrit for code review. The short version of how to patch is:
... edit code ... ninja -C out && out/gn_unittests
Then, to upload a change for review:
git commit git push origin HEAD:refs/for/master # This uploads for review.
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 w/ GN‘s development on Chromium’s gn-dev@ Google Group.