Lines Matching +full:- +full:- +full:build +full:- +full:root

3 This page is about how to design a project that can build independently
4 with GN but also be brought into the Chrome build.
7 configuration that must be the same between both the standalone build
8 and the Chrome build. However, GN is much more explicit in its naming
13 # What you need for a minimal GN build
17   * A master build config file. Chrome's is `//build/config/BUILDCONFIG.gn`
18   * A separate build file for the toolchain definition. It's not a good idea
19     to put these in a BUILD.gn file shared with any target definitions for
20     complex reasons. Chrome's are in `//build/toolchain/<platform>/BUILD.gn`.
21   * A `BUILD.gn` file in the root directory. This will be loaded after the
22     build config file to start the build.
24 You may want a `.gn` file in the root directory. When you run GN it
26 treats the containing directory as the "source root". This file also
27 defines the location of the master build config file:
30   * Unlike Chrome, you probably don't need to define a secondary root.
34 that then running GN in your subdirectory will configure a build for
39 (e.g., to do the full Chrome build instead), you can use the command-line
40 flags `--root` and `--dotfile` to set the values you want.
42 If you want a completely standalone build that has nothing to do with Chrome
43 and doesn't use Chrome's `//build` files, you can look at an example in