| Age | Commit message (Collapse) | Author |
|---|
|
DeviceMaxPageSizeSupported product variable will be used in arm/arm64
targets to configure the binary alignment.
Test: Unit tests
Bug: 276963698
Bug: 276801883
(cherry picked from https://android-review.googlesource.com/q/commit:68470992f2bbdcc5c01fbf28a6407029e38c55bc)
Merged-In: I27168b3343ac383020483eddf907ee71cf084de8
Change-Id: I27168b3343ac383020483eddf907ee71cf084de8
|
|
Load these variables from the product_vars target instead of directly
from the soong.variables file so that it can be transitioned on.
Bug: 269577299
Test: b test --config=android //build/bazel/rules/apex/...
Change-Id: I034da70ab7ce85f467d001e842e0526bb9b99c54
|
|
Revert submission 2529690-revert-2522075-tzdata-test-apex-bazel-RZRVOCMHXM
Reason for revert: fix-forward.
Reverted changes: /q/submissionid:2529690-revert-2522075-tzdata-test-apex-bazel-RZRVOCMHXM
Change-Id: I7dd40639b72054784ba8164307f2abeab5620ab1
|
|
Revert submission 2522075-tzdata-test-apex-bazel
Reason for revert: DroidMonitor: Potential culprit for Bug X - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted
Reverted changes: /q/submissionid:2522075-tzdata-test-apex-bazel
Change-Id: I1346eac36a220feb575bda5a3836ae974726f790
|
|
product config.
- apex manifest package
The package name (not apex name) stamped into AndroidManifest.xml can be
overriden with PRODUCT_MANIFEST_PACKAGE_NAME_OVERRIDES, a
colon-separated list of apex:package_name mapping. For example,
test1_com.android.tzdata:com.google.android.tzdata means that
test1_com.android.tzdata's package name is com.google.android.tzdata,
and can be installed onto a device that has com.google.android.tzdata
preinstalled.
- android_app_certificate
The mapping for the certs used to sign APEX containers is similar to the
apex manifest package mapping, except that the certificates have to be
searched from the DefaultAppCertificate directory. For example,
com.android.tzdata:com.google.android.tzdata.certificate means to use
the Google certificate for signing the container.
This reuses the DefaultAppCertificateFiles filegroup added in a previous
CL for transition-safe product variable accessors.
- apex_key
This is used to sign the apex image (not container). While this doesn't
have a mapping like manifest package and app certificate, it is
influenced by product config as well.
apex_key overriding is simpler. It checks if DefaultAppCertificate is
set, and if so, look for the avbpubkey and pem in that directory.
Otherwise it uses the module dir or the testkey. See config#ApexKeyDir:
https://cs.android.com/android/platform/superproject/+/master:build/soong/android/config.go;l=980-990;drc=7a646211698cc713512bf5046b5bd3ba446143d1
Fixes: b/276416537
Fixes: b/275351675
Test: presubmit
Test: b build test1_com.android.tzdata, adb install onto internal cuttlefish device with com.google.android.tzdata5 preinstalled.
Test: apex key test
Test: abtd
Change-Id: Id9486c4436ea82f1a5ead12a09c198c0c2f7d085
|
|
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
|
