Extra space in variable names causes dependencies for
INSTALLED_VBMETAIMAGE_TARGET to be missing. Remove extraneous sspaces.
Bug: 263568805
Test: lunch cuttlefish, m distclean, m, and check
$OUT/vbmeta_vendor_dlkm.img
Change-Id: If818a8af42c407a7213f58a7142dffb9dee1fd16
Allow building unbundled prebuilts for aosp_riscv64.
Test: TARGET_BUILD_APPS=CtsShim TARGET_PRODUCT=aosp_riscv64 m
Change-Id: If563f2e9b6c0181ad2465367e30bb283bea1fcf9
Only use 8G as default size, when product does not specify
the system image sizes.
Bug: 265440010
Test: build and check sizes
Change-Id: I8da862482600d06eda9b84d0cc5db65f713067b5
By default set `ro.virtual_ab.compression.threads` it to false.
Enabling this will improve OTA install time at the cost
of one more CPU.
Bug: 254188450
Test: OTA on Pixel
Change-Id: Idf1fa950a5fc394f0d783d80c84045295185fb85
Signed-off-by: Akilesh Kailash <akailash@google.com>
For targets with BoardUsesRecoveryAsBoot set to true, binaries in
generic_ramdisk are installed to $OUT/recovery/root/first_stage_ramdisk
This path is not on generic_ramdisk.mk 's allowlist, hence build fails.
To fix the failure, add $OUT/recovery/root/first_stage_ramdisk/system to
allow list.
Test: th, lunch eos-userdebug(a dedicated recovery partition target) and build.
Bug: 265477065
Change-Id: I89cf229adc028a7e5de632b9a3188ecb411de735
Currently we only have vbmeta_system and vbmeta_vendor. Add
BOARD_AVB_VBMETA_CUSTOM_PARTITIONS , which allows OEMs to define
their own vbmeta_*.img partitions. example: aosp/2381823
Bug: 263568805
Change-Id: Id671e2c3aee9ada90256381cce432927df03169b
Even if we were shipping 64-bit Windows host tools (which we still
aren't), this would still be a bug. Windows is LLP64 instead of LP64,
so the long that ftell()/fseek() uses isn't big enough for a 64-bit off_t.
Test: treehugger
Change-Id: I4e24afe811ff9b7d5696887cc5ee92e54e4a3b76
Under some build configuration, there could be build prop stored under
path VENDOR_BOOT/RAMDISK_FRAGMENTS/recovery/RAMDISK/default.prop .
When signing, we must overwrite all build props, or device would display
incorrect build fingerprint.
Bug: 264853953
Change-Id: Id3b176b4ce4efa348ecfb3c9848f72273c5ccca8
This is useful for searching Rust config files in external.
Test: cd external/rust/crates; tomlgrep foo
Change-Id: I1ff5118a8eee1a95f1bc6fa44c922673a03ebd8b
When we have dedicated .mk files for each modules (e.g. usb, drm, etc)
and those modules have their own linker configuration requirements, it
would make more sense to have "fragments" for linker configuration.
This change introduces a new list variable to store the list of linker
configuration fragments. When it's set, vendor/etc/linker.config.pb is
generated from the list of input fragments.
Bug: 264330513
Test: set PRODUCT_VENDOR_LINKER_CONFIG_FRAGMENTS
Test: m vendorimage (generates vendor/etc/linker.config.pb)
Change-Id: I9eed0f90add0191885b7195efdab94b5b1a4a62d
This tidy check has been disabled by default globally,
in build/soong/cc/config/tidy.go.
Local projects can enable it to find/fix such issues,
but if not fixed, it should not be treated as a
high severity one and not to alarm daily builds.
Bug: 227361697
Test: warn.py --url=http://cs/android --separator='?l=' build.log > warnings.html
Test: warn.py --gencsv build.log > warnings.csv
Change-Id: Ifa65a788ddc6a67ed3250d5bed737c6e3b153617
- Move LLNDK dumps from vndk directory to platform directory.
- Rename ndk and platform subdirectories from the codename to "current".
Bug: 238383845
Test: make check-vndk-list
Change-Id: Iafd9c970ebbdcc670c2ec406fda5ae861469a023
