Lines Matching +full:- +full:- +full:default +full:- +full:toolchain

1 # How GN handles cross-compiling
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
26 specify that they want to do a cross-compile by setting either or both
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"'
68 only apply to the current toolchain and the current thing being built.
76 For the default toolchain, `target_cpu` and `current_cpu` are the same. For a
77 secondary toolchain, `current_cpu` is set based on the toolchain definition
81 By default, dependencies listed in the `deps` variable of a rule use the
82 same (currently active) toolchain. You may specify a different toolchain
95   # Uses current_cpu because compile flags are toolchain-dependent.
105       "-isysroot",
112 ## As a //build/config or //build/toolchain author
116 `default_toolchain` should be the toolchain for the `target_os` and
117 `target_cpu`. The `current_toolchain` reflects the toolchain that is currently
123 `current_cpu` is set appropriately in your toolchain definitions; if you