Add support for building .swift files

This CL allow listing .swift files in sources of compiler target
(source_set, executable, static_library, shared_library). Mixing
with other types of source files is disallowed due to complexity
of implementation (difficult to decide in which order the files
need to be built).

This adds a new "swift" tool that must always list a .swiftmodule
file as output but can generate additional outputs (.h, .o, ...).
To support whole module optimisation, the tool can have partial
outputs (i.e. have 1:1 mapping between source and output) or not.

The .swiftmodule are propagated both to direct and public deps
for generation of module search path (expanded by {{module_dirs}})
and to linkable target (expanded as {{modules}}) to embed the
module AST in the linked binary.

Based on the investigation at

Bug: 121
Change-Id: If92b49f15e9ebb273feff7c935ca51698c27afa3
Commit-Queue: Sylvain Defresne <>
Reviewed-by: Brett Wilson <>
36 files changed
tree: 42276d919dfe4d204c529ade2766c004e8d4389a
  1. build/
  2. docs/
  3. examples/
  4. infra/
  5. misc/
  6. src/
  7. tools/
  8. .clang-format
  9. .editorconfig
  10. .gitignore
  11. .style.yapf
  14. OWNERS


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
cd gn
python build/
ninja -C out
# To run tests:

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.


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

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

... edit code ...
ninja -C out && out/gn_unittests

Then, to upload a change for review:

git commit
git push origin HEAD:refs/for/master

The first time you do this you'll get an error from the server about a missing change-ID. Follow the directions in the error message to install the change-ID hook and run git commit --amend to apply the hook to the current commit.

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.