dbcb1ff469
This effectively moves execution of Bazel actions outside of soong_build and alongside ninja execution of the actual ninja files, whether that be by ninja or by Bazel itself. This almost allows for mixed builds and Bazel-as-Ninja-executor to coexist, but requires hacks explained in b/175307058. Test: Treehugger Test: lunch aosp_flame && USE_BAZEL_ANALYSIS=1 m libc Test: lunch aosp_flame && USE_BAZEL=1 USE_BAZEL_ANALYSIS=1 m libc, though this requires a hack of the main BUILD file. See b/175307058 Change-Id: Ia2f6b0f1057e8cea3809de66d8287f13d84b510c
15 lines
262 B
Text
15 lines
262 B
Text
bootstrap_go_package {
|
|
name: "soong-bazel",
|
|
pkgPath: "android/soong/bazel",
|
|
srcs: [
|
|
"aquery.go",
|
|
"constants.go",
|
|
"properties.go",
|
|
],
|
|
pluginFor: [
|
|
"soong_build",
|
|
],
|
|
deps: [
|
|
"blueprint",
|
|
],
|
|
}
|