commit | 0f3dbca6143ec3c4e6e0de9e20f19732c56b81a7 | [log] [tgz] |
---|---|---|
author | Petr Hosek <phosek@google.com> | Thu Apr 11 10:30:18 2019 -0700 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Apr 12 18:03:08 2019 +0000 |
tree | b065f8e20a6c65ff51109b0ba5199efa8ce5b650 | |
parent | 64b846c96daeb3eaf08e26d8a84d8451c6cb712b [diff] |
Use LLVM archiver on macOS macOS libtool doesn't seem to handle LTO object files, use LLVM linker instead to avoid the error. Change-Id: I4a5dd0ee8eb508b86ec2a9431b09f69b8b9d5eb1 Reviewed-on: https://gn-review.googlesource.com/c/gn/+/4600 Reviewed-by: Scott Graham <scottmg@chromium.org> Commit-Queue: Petr Hosek <phosek@google.com>
GN is a meta-build system that generates build files for Ninja. There is documentation in docs/ and a presentation on it.
You can download the latest version of GN binary for Linux, macOS and Windows.
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 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
.
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.