| Age | Commit message (Collapse) | Author |
|---|
|
I realized that we don't need to create all platforms in soong_injection
if we move the product_vars target out of soong_injection as well.
product_vars needs to be a select statement from all the products
to their _product_vars target, so we require all android_product()s
to "register" with that product_vars select statement.
Bug: 269577299
Test: b test --config=android //build/bazel/rules/apex:all
Change-Id: I47456ee1dbcc62af2c11cbff7e2b08152506eb29
|
|
Start storing product config variables in
//build/bazel/product_config:product_vars, starting with CompressedApex.
//build/bazel/product_config:product_vars is an alias to a select
statement that will select the appropriate target to use for the current
android product, so the product config variable will have the correct
value if we transition into another product.
Bug: 269577299
Test: b test --config=android //build/bazel/...
Change-Id: Id148933679c9f3230892766f64fe20312b4802ce
|
|
We create an android_product macro that replaces a lot
of the existing platform code. It takes a soong.variables
file, and creates bazel platforms for the android product,
various other arches, and the host platforms. (currently
host builds still depend on product config variables)
To change products, you'll be able to pass
--platform=//build/bazel/product_config/generated/products/<product_name>,
however currently we only generate the platforms for the
currently lunched product for performance. When the other
products are in starlark, we can allow using all of them.
Bug: 249685973
Test: Presubmits
Change-Id: Ic1b0942a60c66eb3fe2b1aa7a2ff436ec9b3c3fb
|
|
This provides a rough outline for a system_image rule
that can currently contain only apexes.
Bug: 232430910
Test: b test //build/bazel/tests/partitions:image_contains_apex_test --test_output=errors
Change-Id: I89e90972b3be0392719443f16875e431f2b36c23
|
