It supports multiple parallel output directories, each with their own configuration. This allows a developer to maintain builds targeting debug, release, or different platforms in parallel without forced rebuilds when switching.
It has a focus on correctness. Although small projects successfully use GN, the focus on large projects has some disadvanages:. GN has the goal of being minimally expressive. Although it can be quite flexible, a design goal is to direct members of a large team who may not have much knowledge about the build down an easy-to-understand, well-lit path.
This isn't necessarily the correct trade-off for smaller projects. The minimal build configuration is relatively heavyweight. There are several files required and the exact way all compilers are linkers are run must be specified in the configuration see "Examples" below.
There is no default compiler configuration. It is not easily composable. GN is designed to compile a single large project with relatively uniform settings and rules. Projects like Chromium do bring together multiple repositories from multiple teams, but the projects must agree on some conventions in the build files to allow this to work. GN is designed with the expectation that the developers building a project want to compile an identical configuration.
So while builds can integrate with the user's environment like the CXX and CFLAGS variables if they want, this is not the default and most project's builds do not do this.
The result is that many GN projects do not integrate well with other systems like ebuild. There is no simple release scheme see "Versioning and distribution" below. Projects are expected to manage the version of GN they require. Getting an appropriate GN binary can be a hurdle for new contributors to a project. Since it is relatively uncommon, it can be more difficult to find information and examples.
Other languages can be compiled using the general "action" rules which are executed by Python or another scripting language Google does this to compile Java and Go. But because this is not as clean, generally GN is only used when the bulk of the build is in one of the main built-in languages. You can download the latest version of GN binary for Linux , macOS and Windows from Google's build infrastructure see "Versioning and distribution" below for how this is expected to work.
On Windows, it is expected that cl. 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:.
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. We ask that all contributors sign Google's Contributor License Agreement either individual or corporate as appropriate, select 'any other Google project'. Most open-source projects are designed to use the developer's computer's current toolchain such as compiler, linker, and build tool.
But the large centrally controlled projects that GN is designed for typically want a more hermetic environment. They will ensure that developers are using a specific compatible toolchain that is versioned with the code. As a result, GN expects that the project choose the appropriate version of GN that will work with each version of the project. There is no "current stable version" of GN that is expected to work for all projects. Some of these systems to have GN packages, but they are maintained by third parties and you should use at your own risk.
Instead, we recommend you refer your checkout tooling to download binaries for a specific hash from Google's build infrastructure or compile your own. GN does not guarantee the backwards-compatibility of new versions and has no branches or versioning scheme beyond the sequence of commits to the master git branch which is expected to be stable. In practice, however, GN is very backwards-compatible. It has a focus on correctness. GN has the goal of being minimally expressive.
Although it can be quite flexible, a design goal is to direct members of a large team who may not have much knowledge about the build down an easy-to-understand, well-lit path.
This isn't necessarily the correct trade-off for smaller projects. The minimal build configuration is relatively heavyweight. There is no default compiler configuration. It is not easily composable. GN is designed to compile a single large project with relatively uniform settings and rules. Projects like Chromium do bring together multiple repositories from multiple teams, but the projects must agree on some conventions in the build files to allow this to work.
GN is designed with the expectation that the developers building a project want to compile an identical configuration. The result is that many GN projects do not integrate well with other systems like ebuild. Projects are expected to manage the version of GN they require. Getting an appropriate GN binary can be a hurdle for new contributors to a project.
Since GN is relatively uncommon, it can be more difficult to find information and examples. But because this is not as clean, generally GN is only used when the bulk of the build is in one of the main built-in languages. On Windows, it is expected that cl. 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 hosted at gn-review. The short version of how to patch is:. 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. But the large centrally controlled projects that GN is designed for typically want a more hermetic environment. They will ensure that developers are using a specific compatible toolchain that is versioned with the code.
As a result, GN expects that the project choose the appropriate version of GN that will work with each version of the project. Some of these systems to have GN packages, but they are maintained by third parties and you should use them at your own risk. Instead, we recommend you refer your checkout tooling to download binaries for a specific hash from Google's build infrastructure or compile your own.
0コメント