|author||Byoungchan Lee <email@example.com>||Tue Dec 10 13:42:09 2019 +0900|
|committer||Commit Bot <firstname.lastname@example.org>||Fri Dec 13 15:38:48 2019 +0000|
Fix quoting preprocessor defines for compilation database If a preprocessor define has a space character, which usually happens with double-quoted text, current compilation database writer cannot handle correctly. These spaces should be escaped. Tested that gn is generating correctly compile_commands.json on WebRTC with Linux. Bug: gn:109 Change-Id: I4ba2ed4c807e4cb9e078720df3b64834a4f9ec8e Reviewed-on: https://gn-review.googlesource.com/c/gn/+/6780 Reviewed-by: Brett Wilson <email@example.com> Commit-Queue: Brett Wilson <firstname.lastname@example.org>
GN is a meta-build system that generates build files for Ninja.
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
There is a simple example in examples/simple_build directory that is a good place to get started with the minimal configuration.
To build and run the simple example with the default gcc compiler:
cd examples/simple_build ../../out/gn gen -C out ninja -C out ./out/hello
For a maximal configuration see the Chromium setup:
and the Fuchsia setup:
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 push origin HEAD:refs/for/master
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 with GN‘s development on Chromium’s gn-dev@ Google Group.