|author||Roland McGrath <firstname.lastname@example.org>||Fri May 17 23:59:56 2019 -0700|
|committer||Commit Bot <email@example.com>||Sun May 19 08:25:16 2019 +0000|
[gen.py] Use relative -I switches and source paths This both makes the ninja files relocatable after gen.py and fixes the case where the output directory was specified as a relative path (which previous didn't have the right -I). Change-Id: I0b01677927a6c7733ae5cb2f731d5d62cb2200ab Reviewed-on: https://gn-review.googlesource.com/c/gn/+/5040 Commit-Queue: Petr Hosek <firstname.lastname@example.org> Reviewed-by: Petr Hosek <email@example.com>
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.