Lines Matching +full:default +full:- +full:build

1 # How GN handles cross-compiling
6 multiple architectures in a single build (e.g., to build some things to
8 there is no limit on the number of different architectures you can build
9 at once; the Chromium build uses at least four in some configurations.
12 the platform that the build is run on, and the target is the platform
18 (Confusingly, GN also refers to each build artifact -- an executable,
19 library, etc. -- as a target. On this page, we will use "target" only to
21 other synonym to refer to a specific build artifact).
26 specify that they want to do a cross-compile by setting either or both
27 of `target_os` and `target_cpu`; if they are not set, the build config
29 build will set target\_cpu to "arm" if target\_os is set to "android").
34 gn gen out/Default
40 gn gen out/Default --args='target_os="linux" target_cpu="x64"'
43 To do an 32-bit ARM Android cross-compile, do:
46 gn gen out/Default --args='target_os="android"'
52 And, to do a 64-bit MIPS Chrome OS cross-compile:
55 gn gen out/Default --args='target_os="chromeos" target_cpu="mips64el"'
58 ## As a BUILD.gn author
60 If you are editing build files outside of the //build directory (i.e.,
76 For the default toolchain, `target_cpu` and `current_cpu` are the same. For a
81 By default, dependencies listed in the `deps` variable of a rule use the
95   # Uses current_cpu because compile flags are toolchain-dependent.
105       "-isysroot",
112 ## As a //build/config or //build/toolchain author
115 projects this normally is in the `//build/config` directory). Usually the