mkfs warns about unknown "selabel=" fields, and this should be coming
from the file_contexts file, not here.
Test: treehugger
Change-Id: I63f3f616a2588438017e609a1a08c9dd7bf0c2ed
Current logic recursively copies $(PRODUCT_OUT)/data into $(PRIVATE_STAGING_DIR)/data
This leads to creating $(PRIVATE_STAGING_DIR)/data/data on incremental
builds causing emulator to fail to boot.
Test: Build emulator sdk_addon twice, extract the zip, run the emulator
and verify it boots and reaches homescreen
Change-Id: I9e74d2ab28f9fbd67362578672d25d438fad0d53
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
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
Change-Id: I9949fb7075ab6c207a292f13fd75e010a4958f87
Some devices would like to use sources of mainline modules
even in next builds. This CL uses PRODUCT_MODULE_BUILD_FROM_SOURCE to
ignore the apex_contributions specified in the shared google_device's next.scl
Long term, this will be implemented by creating a product specific
release config map for this family of devices
Test: lunch <device>_fullmte-next-userdebug && m nothing
Bug: 325666427
Ignore-AOSP-First: The CL touches an internal only allowlist
Change-Id: I0cabba5faa4535dcdff3aa8b87aa61ac06ac9edb
This CL removes the SYSTEMUI_USE_COMPOSE build flag, which is now
enabled by default on all SystemUI variants.
Bug: 295304993
Test: mp droid
Ignore-AOSP-First: Flag was introduced in internal tree in
ag/20785186
Change-Id: I2f2b6b66262eefe2f0b0821773fda4cc07526d7b
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 change puts base_system and default_art_config references to
the profiling module behind the build flag.
It also adds the flag to soong_config_vars so it can be referenced
from the Profiling module and from platform_bootclasspath.
Bug: 293957254
Bug: 325523640
Test: Built locally on trunk_food (where flag is disabled) and
trunk_staging (where flag is enabled.)
Ignore-AOSP-First: Must be submitted in topic with internal-only
changes.
Change-Id: I51cfa65ff607753cc8c588793ea381419ac99260
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
