Using standard naming to be consistent with the rest of the bp2build workspace.
Test: b build //build/core/...
Change-Id: If81a8fb82ccd3f63d0961f8a4a37ca8be7aa4430
Rather than copying GKI modules from source folder
pointed by BOARD_SYSTEM_DLKM_SRC; use core build
macro BOARD_SYSTEM_KERNEL_MODULES as list
of GKI modules to be copied on the system_dlkm partition.
This leverages core infrastructre already present for
the kernel modules for vendor_dlkm, odm_dlkm, etc.
Bug: 232430739
Test: TH
Change-Id: Ic53f450eb426dc4ec38fc80b7ceaa625c8ab206b
Signed-off-by: Ramji Jiyani <ramjiyani@google.com>
There is a lot of policy cruft left around to support this. We
would like to simplify the number of supported options, so doing
this as an advanced notice.
Bug: 257176017
Test: build
Change-Id: I1c4350fb3a075118be62d75cc1351eb20e584749
Now, checkvintf finds input file from dirmaps. We don't need to pass
around --apex-info-file.
dump_apex_info also generates files under /apex without an explicit
--out_file argument.
This makes "make" know less about coupling between dump_apex_info
and checkvintf.
Bug: 260310732
Test: manually run check_target_files_vintf -v target-files
Change-Id: Ibfe31978e983e13df35c32521913d5cbc89dc1d1
Isolated TF tests are failing since the `--add-exports` option cannot be
parsed by JDK 17+ due to a missing '<target-module>' component. This
change resolves the issue by adjusting the options in the TF template to
export the source package to all unnamed modules.
See
https://docs.oracle.com/javase/9/migrate/toc.htm#JSMIG-GUID-2F61F3A9-0979-46A4-8B49-325BA0EE8B66
for more information.
Test: atest --host HelloWorldHostTest
Change-Id: Iccb8a8dcd3707237e018d6feb6b6a0e8d2bc9a86
Revert the previous script changes, run the finalization, and then the
build.
Useful to cross check the broken branch - do we just need to re-run the
script, or is there a bigger problem.
Bug: 243966946
Test: run locally
Change-Id: I44d6a5f5f523001ae70e5b82315ffbad82a1233d
aosp_riscv64 doesn't use base-system.mk yet, add init_first_stage
to the ramdisk manually.
Test: lunch aosp_riscv64-userdebug && m out/target/product/generic_riscv64/ramdisk.img
Change-Id: I148e436b34e8900815eb8dac42a6c1f5251f824d
This is determined by:
- a product config flag
- the vendor API level
It is then passed to the device as a system property
"ro.dalvik.vm.enable_uffd_gc".
This change is a no-op change. It doesn't enable userfaultfd GC by
default. OVERRIDE_ENABLE_UFFD_GC=default can be passed to the build
system to enable userfaultfd GC for testing purposes.
Bug: 242553398
Test: -
1. lunch aosp_redfin-userdebug
2. OVERRIDE_ENABLE_UFFD_GC=default build/soong/soong_ui.bash --dumpvars-mode --vars=ENABLE_UFFD_GC
3. See "false" in the output
Test: -
1. lunch aosp_oriole-userdebug
2. OVERRIDE_ENABLE_UFFD_GC=default build/soong/soong_ui.bash --dumpvars-mode --vars=ENABLE_UFFD_GC
3. See "true" in the output
Test: -
1. lunch aosp_redfin-userdebug
2. OVERRIDE_ENABLE_UFFD_GC=true build/soong/soong_ui.bash --dumpvars-mode --vars=ENABLE_UFFD_GC
3. See "true" in the output
Test: -
1. lunch aosp_oriole-userdebug
2. OVERRIDE_ENABLE_UFFD_GC=false build/soong/soong_ui.bash --dumpvars-mode --vars=ENABLE_UFFD_GC
3. See "false" in the output
Change-Id: Ifd6e6cddb502315912ff949619a5b526ae0d73ff
Just a shuffle to avoid a merge conflict
Test: make
Merged-In: Id68e4ef3b38965c08c9b783d32ccc2aca342ed24
Change-Id: Ia7945144227cb7c23e727a4c490d443ba28b9abf
The change in the packages/modules/Virtualization in the same topic
takes care for defining the right variant of the APEX to be installed:
* Devices with AVF support will get the full com.android.virt APEX
* Devices without AVF support will get an almost empty version that only
contains an app that defines AVF-related permissions, and soon the BCP
fragment jar.
Bug: 243512044
Test: build & flash oriole
Test: build & flash redfin
Change-Id: I2c38e03529a77dd2820212812433741725115ce0
When building an incremental OTA package, if the compress_target=True
parameter is passed in when calculating a block, an exception will occur
in the subsequent join operation.
The reason is that Python 3 no longer allows str type join bytes type.
Bug: None
Test: Build Incremental OTA package
Change-Id: I6d556f9905b7ab75b70d3785334d71d5a6e5479b
Signed-off-by: luoqiangwei1 <luoqiangwei1@xiaomi.com>
There are still devices that set BUILD_BROKEN_USES_BUILD_HOST_* and
build host modules in Make. Add basic support for building against
libc_musl in Make when USE_HOST_MUSL is set.
Bug: 258535366
Test: build a host tool defined in Android.mk file in internal branch
Change-Id: I9150be749bbeaac2ac5a33b2cf915004aa3033df
Currently, when merging target files, system side's update_engine
version info is copied into the merged target_files. This causes
recovery OTA failure, because update_engine_sideload daemon in recovery
is from vendor side. To fix it, use the older version of update_engine
config when merging target files.
Test: th
Bug: 257426678
Change-Id: I5d3304366749995c99a61ca0645a22ee047f1465
`lib` is already a string and doesn't need to be decoded.
Bug: 258395719
Test: On internal master: build/soong/soong_ui.bash --make-mode --bazel-mode-staging TARGET_PRODUCT=aosp_coral TARGET_BUILD_VARIANT=userdebug droid dist device-tests platform_tests
Change-Id: I83ff35339bea9f01c61d953e251788e0894005dc
