Clone this repo:


  1. a51d79f Remove reference to deleted sequenced_worker_pool by Tim Brown · 33 hours ago master
  2. bd5a270 Rename buildflag_header targets in base for consistency by Scott Violet · 3 days ago
  3. b52620a gn: Write no stamp files for action inputs. by Nico Weber · 12 days ago
  4. ec876d0 Fix gn reference in after bootstrapping by Tom Anderson · 2 weeks ago
  5. fe4c8a2 Support for JSON input conversion by Petr Hosek · 2 weeks ago

What is GN?

GN is a meta-build system that generates Ninja build files so that you can build Chromium with Ninja.

Why did you switch from GYP?

  1. We believe GN files are more readable and more maintainable than GYP files.
  2. GN is fast:
  • GN is 20x faster than GYP.
  • GN supports automatically re-running itself as needed by Ninja as part of the build. This eliminates the need to remember to re-run GN when you change a build file.
  1. GN gives us better tools for enforcing dependencies (see gn check and the visibility, public_deps, and data_deps options for some examples).
  2. GN gives us tools for querying the build graph; you can ask “what does X depend on” and “who depends on Y”, for example.

What's the status of the GYP->GN migration for Chromium?

As of Oct 2016:

  • All of the Chromium builds have been switched over.
  • Nearly all of the GYP files have been deleted from the Chromium repos.
  • You can no longer build with GYP as a result.
  • There are still some GYP files in place for the “Closure Compilation” builders that need to be converted over.
  • Some related projects (e.g., V8, Skia) may still support GYP for their own reasons.
  • We're still cleaning up some odds and ends like making gclient not still use GYP_DEFINES.

I want more info on GN!

Read these links: