|author||Julie Hockett <email@example.com>||Mon Jun 10 16:41:17 2019 -0700|
|committer||Commit Bot <firstname.lastname@example.org>||Fri Jun 14 21:00:44 2019 +0000|
Add command_launcher field to tools This is a field to specify the command launcher for a given tool's command. It appends the launcher to the command in the Ninja rule, but keeps the two separate inside of GN. This allows the IDE writer tools (e.g. the compilation command database) to be written without the launcher prefix. The presence of the launcher in the command has been breaking a number of developer workflows in VSCode, CLion, and clangd. This should resolve all of those workflows. Change-Id: Idec6f530ddc48da01ac0c79b64032c7cc88856a4 Reviewed-on: https://gn-review.googlesource.com/c/gn/+/5200 Commit-Queue: Julie Hockett <email@example.com> Reviewed-by: Petr Hosek <firstname.lastname@example.org> Reviewed-by: Brett Wilson <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.