Lines Matching refs:to
10 Android Platform build system, and how each component maps to a concept in
13 |Android build system component|Description|Mapping to Bazel concepts|
15 …ates Ninja file directly.|Loading and analysis phase. Conceptually similar to `bazel build --nobui…
17 …lueprint to generate Ninja file. Generates a `.mk` file with prebuilt module stubs to Kati.|Loadi…
19 |atest|Test executor and orchestrator.|Conceptually similar to `bazel test` command.|
20 … Ninja + atest|The entire build pipeline for Android.|Conceptually similar to `bazel build` or `ba…
21 |`<script>.sh`|Running arbitrary scripts in AOSP.|Conceptually similar to `bazel run` command.|
22 …the tools above.|Loading, analysis, execution phases. Conceptually similar to `bazel build` comman…
28 * Kati product configuration component to generate config variables (config.mk, AndroidProducts.mk)
30 * Kati component to generate build actions in Ninja files (main.mk, Android.mk files)
32 * Kati component to generate packaging actions in Ninja files (packaging.mk file)
34 * Kati component to generate cleaning actions in Ninja files (cleanbuild.mk, CleanSpec.mk files)
36 * **soong\_build** (and **Blueprint**) component to generate build actions (Android.bp, Blueprints …
37 * **Ninja** component to execute actions from Kati-build, Kati-package and soong\_build
39 * **soong\_ui** as the tool to orchestrate all of the above, and with auxiliary tools like finder, …
53 1. soong\_ui runs auxiliary tools to aggregate files into filelists, for
57 1. soong\_ui orchestrates 3 Blueprint/Soong phases to generate the main out/soong/build.ninja file:
59 1. Minibootstrap phase uses Blueprint/Microfactory to build itself
60 (minibp) so that Android.bp and Blueprint files can be used to define
62 1. Bootstrap phase runs Ninja on a build.ninja file that runs minibp to
66 to generate the final out/soong/build.ninja file.
72 1. soong\_ui runs Kati-build to generate a Ninja file, with
74 1. soong\_ui runs Kati-package to generate a Ninja file, with
77 1. soong\_ui generates a Ninja file to combine above Ninja files.
78 1. soong\_ui runs either Ninja or Bazel to execute the build, with the
93 soong\_ui uses finder.go to generate <filename>.list files for other
98 soong\_ui uses path\_interposer to prepare an hermetic $PATH with runtime
100 tools with checked-in prebuilts, and uses path\_interposer to intercept calls
104 soong\_ui generates a Kati suffix to ensure that Kati-generated files are
105 regenerated if inputs to Kati have changed between builds.
107 soong\_ui calls Soong and Kati to generate Ninja files, and eventually
108 creates another Ninja file (out/combined-<product>.ninja) to combine the
109 others, and executes either Ninja or Bazel to complete the build.
117 to dump the values of specified Make variables at the end of an evaluation,
121 to generate the **[soong.variables JSON
123 This way, Kati-config can communicate product configuration to soong\_build,
129 variables to soong\_build, [dexpreopt.config is also
136 soong\_ui sets up a **KatiReader** to monitor Kati-config’s stdout/err for UI
141 soong\_build’s primary role is to evaluate all Android.bp files, run a series
145 the AndroidMk singleton to generate .mk files in the output directory
151 from Soong modules. There are also checks built into this .mk file to ensure that
156 * soong\_ui invokes Kati to parse make\_vars .mk file earlier than the Android.mk
158 * late.mk is used to define phony rules to take advantage of Make’s ability to
159 add extra dependencies to an existing rule. late.mk is not strictly necessary to
165 Kati-build’s primary role is to evaluate all Android.mk files with
168 product, containing statements on how to remove stale output files.
170 Kati-build’s primary role is to evaluate all packaging .mk files with
176 KatiReader to UI and error handling.
180 wrappers for soong\_ui to execute Ninja with the correct Ninja files, in a
186 bootstrapping tools like Blueprint, it writes to a fifo in a proto front end
192 As more Soong modules are converted to BUILD files, soong\_build serializes
193 information about converted modules to BUILD/bzl files on disk. soong\_build
195 the Bazel client to issue `cquery` calls about these targets.