The generated module lets us keep the aconfig code in its own pacakge and not infect all of the cc package with aconfig. It's also closer to what bazel is going to do Bug: 283479529 Test: m aconfig_hello_world_cc && adb push $TOP/out/target/product/panther/system/bin/aconfig_hello_world_cc /system/bin && adb shell aconfig_hello_world_cc Change-Id: I2fb9e419939c7ca77b111da9c376af077e2348a9
35 lines
794 B
Plaintext
35 lines
794 B
Plaintext
package {
|
|
default_applicable_licenses: ["Android-Apache-2.0"],
|
|
}
|
|
|
|
bootstrap_go_package {
|
|
name: "soong-aconfig",
|
|
pkgPath: "android/soong/aconfig",
|
|
deps: [
|
|
"blueprint",
|
|
"blueprint-pathtools",
|
|
"sbox_proto",
|
|
"soong",
|
|
"soong-android",
|
|
"soong-bazel",
|
|
"soong-android",
|
|
"soong-java",
|
|
],
|
|
srcs: [
|
|
"aconfig_declarations.go",
|
|
"aconfig_values.go",
|
|
"aconfig_value_set.go",
|
|
"all_aconfig_declarations.go",
|
|
"cc_aconfig_library.go",
|
|
"init.go",
|
|
"java_aconfig_library.go",
|
|
"testing.go",
|
|
],
|
|
testSrcs: [
|
|
"aconfig_declarations_test.go",
|
|
"aconfig_values_test.go",
|
|
"aconfig_value_set_test.go",
|
|
],
|
|
pluginFor: ["soong_build"],
|
|
}
|