win: Don't use rsp files when compiling gn.

Compile command lines are pretty short; even chromium doens't need rsp
files for them.

Makes the build a tiny bit faster because rsp files are written by
ninja on the critical path, and makes the build a bit easier to
work with since it's now easier to copy-paste failing compile
commands.

While here, also remove some needless braces, to make the file
more similar to linux/mac.

No intended behavior change.

Change-Id: I696b0f8d8b911e76cd5cde3c0e331375e2a766f1
Reviewed-on: https://gn-review.googlesource.com/c/gn/+/6441
Reviewed-by: Scott Graham <scottmg@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
1 file changed
tree: 081e63d951c94cd0b35bdc408d3bb8498701e531
  1. base/
  2. build/
  3. docs/
  4. examples/
  5. infra/
  6. tools/
  7. util/
  8. .clang-format
  9. .editorconfig
  10. .gitignore
  11. .style.yapf
  12. AUTHORS
  13. LICENSE
  14. OWNERS
  15. README.md
README.md

GN

GN is a meta-build system that generates build files for Ninja.

Related resources:

Getting a binary

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.

Examples

There is a simple example in examples/simple_build directory that is a good place to get started with the minimal configuration.

For a maximal configuration see the Chromium setup:

and the Fuchsia setup:

Reporting bugs

If you find a bug, you can see if it is known or report it in the bug database.

Sending patches

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’).

Community

You may ask questions and follow along with GN‘s development on Chromium’s gn-dev@ Google Group.