mkfs warns about unknown "selabel=" fields, and this should be coming
from the file_contexts file, not here.
Test: treehugger
Change-Id: I63f3f616a2588438017e609a1a08c9dd7bf0c2ed
The time needed for executing shell code strongly depends on how many
times the shell has to call fork(). Hence, instead of invoking 'basename'
once per kernel module, invoke 'basename' once for all kernel modules.
Change-Id: Ibe322c8ebf0a466568f902beb5ab91988381678c
Signed-off-by: Bart Van Assche <bvanassche@google.com>
Different prebuilts might have different contents and thus, different
boot jars to be removed from the existing apex boot jar lists e.g. next
using U prebuilts would need to remove framework-pdf while ap31 with V
prebuilts must not remove such. The existing mechanism will always
remove framework-pdf whenever prebuilts are enabled regardless of
release config, which is not correct in context of multiple prebuilt
support.
Ignore-AOSP-First: for successful build, we need to submit this togther with ag/26332775. this cl will get cp'ed into aosp later on
Bug: 327022391
Test: build device in next and trunk
Merged-In: I9949fb7075ab6c207a292f13fd75e010a4958f87
Change-Id: I9949fb7075ab6c207a292f13fd75e010a4958f87
The 1p files are included in PRODUCT_COPY_FILES and released with products.
Bug: 316805918
Test: CIs
Change-Id: Ibe443af26fb14c1bd84552c9f327a1c2ba8c70a4
Devices may set its first vendor api level to
PRODUCT_SHIPPING_VENDOR_API_LEVEL. This will manually set to
ro.vendor.api_level and will be used by tests.
If this value is not defined, init process will automatically
calculate the ro.vendor.api_level property for tests.
Bug: 326164316
Test: Check vendor/build.prop
Change-Id: I89f844ffaad9e3e39deab1c680bd1f7f17f4d8ad
This silences warnings such as:
linker: Warning: failed to find generated linker configuration from "/linkerconfig/ld.config.txt"
WARNING: linker: Warning: failed to find generated linker configuration from "/linkerconfig/ld.config.txt"
that are printed at the start of every command in the first
stage console.
Change-Id: I3d820e4960a4dbca34369223aed83589534c2eb6
PRODUCT_EXPORT_RUNTIME_APIS is a product variable that inherits the
behavior of the build flag RELEASE_EXPORT_RUNTIME_APIS, which is being
removed. This will be utilized in the product `sdk_with_runtime_apis`,
which will be introduced in a future change.
Test: m nothing --no-skip-soong-tests
Bug: 326312949
Change-Id: I4966b7bfc7423db049acfcede67233352ba8341b
The new product variable behaves identical to the build flag
RELEASE_HIDDEN_API_EXPORTABLE_STUBS: if the variable is set to true, the
hiddenapi flags are generated from the "exportable" stubs (i.e. the
stubs that does not include READ_WRITE permission or DISABLE state
flagged apis) instead of the "everything" stubs (i.e. the stubs that
includes all flagged apis regardless of the state of the flags). If the
variable is set to false, the stubs are generated from the "everything"
stubs.
This product variable will be utilized for `sdk_with_runtime_apis`
product in the future changes.
Test: m nothing
Bug: 326310637
Change-Id: Iab3b46ac39972b8721d3aa07cec622c57dafbd0e
Otherwise system_ext.img wouldn't be built under $PRODUCT_OUT dir when
building a system.img&system_ext.img only build target.
Bug: 326359088
Test: Build a system/system_ext image only target
Change-Id: I8732f7a578350f8bc3b91f8a1db656bf95eddc95
There's no point testing the system vintf boundary on a system image
-less target.
Bug: 326354182
Bug: 326359088
Test: Build a system image -less target
Change-Id: I1ef71f93acb1e7a6252ae14e18c30cb23cb08db2
Right now write-file-lines is defined only if BUILDING_SYSTEM_IMAGE is
true. This means split build / partial build targets that doesn't build
the system image, would fail to build other partition images too
because the $(<parttition>image_intermediates)/file_list.txt build rule
would be undefined.
Move the macro definition out of the `ifdef BUILDING_SYSTEM_IMAGE`
conditional block.
Bug: 326359088
Test: build a target that doesn't build system image
Change-Id: I020c28f7011bd0df0330ba3350e50bea2b75aab4
Files need to be moved from platform to the new apex.
Adding a flag to control this movement.
More Details: go/conditionally-move-android-files
Bug: b/289203818
Test: m
Change-Id: Id3674bd6a8a32f64d189b8ac17b222b9d7966f69
Merged-In: Id3674bd6a8a32f64d189b8ac17b222b9d7966f69
We have more known codenames then we are releasing, and need a way to
override this in release configs.
Bug: 307733231
Test: m nothing
Change-Id: I2215dc449ca28cae253f514183507550b58f267b
Merged-In: I2215dc449ca28cae253f514183507550b58f267b
(cherry picked from commit 569b9e08fa)
