Lines Matching refs:target

28 # represents the computer doing the compile and never changes. The "target"
31 # host, the target, or something completely different (like nacl). GN will
42 # concept, and "target" is something our build sets up that's symmetrical with
184 # - If your feature is a single target, say //components/foo, you can put
190 #   the buildflag_header target in the same file as the build flag itself. You
193 # - If your flag toggles a target on and off or toggles between different
194 #   versions of similar things, write a "group" target that forwards to the
195 #   right target (or no target) depending on the value of the build flag. This
240   # Allows the path to a custom target toolchain to be injected as a single
248   # target platform
557   # Set up the default configuration for every build target of the given type.
559   # corresponding target. Target definitions can add or remove to the settings
824     target(_target_type, target_name) {
848       target(_target_type, target_name) {