| commit | f0b4405f4e0809bcc4bb90644eccae4c806b7cd6 | [log] [tgz] |
|---|---|---|
| author | Nico Weber <thakis@chromium.org> | Mon Jul 09 12:33:20 2018 -0400 |
| committer | Commit Bot <commit-bot@chromium.org> | Mon Jul 09 16:43:40 2018 +0000 |
| tree | 2be0792ad27eba1eff40001dcfe414a084736119 | |
| parent | 9911c78235919577170575f6447554927fdc4a64 [diff] |
Don't pass -flto. It was added recently in https://gn-review.googlesource.com/c/1820/ for minor performance gains, but it makes linking gn take a long time which is painful for development, and it makes clang either depend on using lld or having LLVMgold.so around, which isn't always the case. Change-Id: Iebca33161f33ad0666d2d3ee0913e51d56cdcc9f Reviewed-on: https://gn-review.googlesource.com/2120 Reviewed-by: Brett Wilson <brettw@chromium.org> Commit-Queue: 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.
TODO: AUTHORS, CLA, etc.