Pass PRODUCT_ART_TARGET_INCLUDE_DEBUG_BUILD to Soong so it can decide if
ART debug APEX should be used instead of ART APEX
Bug: 351698657
Test: AOSP CF eng build succeeded
Change-Id: I1e0683be5cd66f1a18e7aec5b1d96ac6e5f4588a
If you don't, release-config will read the TARGET_PRODUCT environment
variable to determine the product. This works in most cases, but it's
possible (e.g. via buildspec.mk) to change the target product within
make without modifying the environment variable. In these cases,
release-config will produce the config for one product but then the
build will read the config for a completely different product, leading
to build errors.
Instead, just pass the target product to release-config explicitly so it
generates the config for the product that the build is expecting.
Bug: 353351911
Test: TARGET_SKIP_OTA_PACKAGE="true" build/soong/soong_ui.bash \
--make-mode TARGET_PRODUCT=apps TARGET_RELEASE=next \
TARGET_BUILD_VARIANT=user droid dist \
ANDROID_BUILDSPEC=vendor/google_clockwork/build/app_build_spec.mk \
ALLOW_MISSING_DEPENDENCIES=true \
UNBUNDLED_BUILD_SDKS_FROM_SOURCE=true \
RELAX_USES_LIBRARY_CHECK=true
Flag: EXEMPT bugfix
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:310d7718439d074fe38b25b97eb609f6db66c3d6)
Merged-In: I63e80249ac702b5517f4a3cfd54c8a4dbd416794
Change-Id: I63e80249ac702b5517f4a3cfd54c8a4dbd416794
`SANITIZE_TARGET` is a variable in Android's build system used to
enable sanitizers. Currently, Soong only supports enabling SANITIZE for
individual modules in Android.bp.
Adding ASAN_ENABLED and SANITIZE_TARGET_SYSTEM_ENABLED as Soong config
variables would allow Soong to also support building with Sanitizers by
directly setting the SANITIZE_TARGET environment variable.
Bug: 353164536
Test: SANITIZE_TARGET_SYSTEM=true SANITIZE_TARGET=address m -j asan_extract
Change-Id: I542239ee25d210d903d2481a2b1426f756656308
This variable allow customizing whether the `ramdisk` and
`vendor_ramdisk` are included in the boot image (ramdisk) or the
vendor boot image (vendor_ramdisk). This is useful for devices that
move recovery resources to the vendor boot partition
Bug: 347636127
Test: Add it to soong_config_module_type
Change-Id: If7a126fe8bdc69173921c0b01f85fb9480f4a36f
** This CL reapplies aosp/3150696. Now it is connected to a
corresponding change in rust soong module to ensure system test dir does
not change to avoid b/350479879. **
Make the template more consistent with the native (aka cc) test temlate.
The important change is that vendor tests will be pushed into
/data/local/tests/vendor.
Having the test binary in the vendor test folder makes the linker treat
it as a vendor binary and prefer vendor libraries. Previously, the test
binary was always a system binary (due to being in /data/local/tmp) and
used system libraries first potentially leading to bugs (e.g. the one
attached).
This change also makes vendor tests that use vendor libraries require
root due to an existing SELinux policy issue with atest.
Bug: 347370677
Test: checked with:
- libsecretkeeper_core_test
- libauthgraph_boringssl_test
- libdice_policy.test
Test steps:
atest -d <test>.vendor # runs vendor variant, passes
adb root
adb shell find / -iname <test> 2>/dev/null
# before change: /data/local/tmp/<test>
# after change: /data/local/tests/vendor/<test>
Test: v2/android-kvm-team/avf_presubmit_tests
Change-Id: I19793bd20bc23ff0c78e622bc6b93f9a90d725c0
By `USE_SOONG_DEFINED_SYSTEM_IMAGE`, a system image specified by
PRODUCT_SOONG_DEFINED_SYSTEM_IMAGE will replace $OUT/system.img.
Bug: 350599472
Test: USE_SOONG_DEFINED_SYSTEM_IMAGE=true m && cvd start
Change-Id: I294ea5e1ce7f9273d0dafc440320b8f194ccf5ca
Downstream testing infra needs per test module folder to be
self-contained to prune dependencies and increase testing efficiency.
Bug: 351909435
Test: presubmit
Change-Id: Icda8982af8eb223ba4ae45be7975dc5aa42a183e
Desktop currently has a custom pack image script that is valuable
to run in pre/post-submit builders. Add hook to the core Makefile
to allow running it.
Bug: b:349581445
Test: m
Change-Id: I368d3c8278beeee9f5c3e863043869c18e773728
When target sets TARGET_BOOTS_16K, it should boot
with 16KB page size. Adding system property based on TARGET_BOOTS_16K.
Test: m Vts16KPageSizeTest && atest -c Vts16KPageSizeTest
Flag: TEST_ONLY
Bug: 350993987
Change-Id: I72c55261ad8d67dfa6be7374e1acd6baddbb3342
This is a fixed version of commit a8f0bb8df8
which was reverted recently by commit 88d65e514c.
To be concise, the code that was moved need to be outside of block "ifneq ($(BOARD_KERNEL_MODULES_16K),)"
in order for non 16K builds to have no errors.
Bug: 349524000
Change-Id: I6264c984837b8aa479c353abee1526bab2dd83ec
Signed-off-by: cactusnoh <cactusnoh@gmail.com>
DTBO taget definition is unintionally moved inside
ifdef BUILDING_RAMDISK_IMAGE guard by aosp/3150938 . This causes
some targets to miss dtbo building if they don't define a ramdisk.
Test: th
Bug: 350056336
Change-Id: If840cc57af794b7844593eeed5935f5e10567e3f
Remove the otacerts module defined in Android.mk. Instead, provide
variables to soong.
Bug: 335364209
Test: Define "PRODUCT_DEFAULT_DEV_CERTIFICATE := \
build/make/target/product/security/testkey" and
m aosp_cf_system_x86_64
Change-Id: I99a484e04984da8bd7f58deecd90c880de16fd71
The PRODUCT_BOOTS_16K is removed and will be
replaced by TARGET_BOOTS_16K variable.
The TARGET_BOOTS_16K will drive the kernel and
modules to use instead.
Bug: 350529323
Bug: 346868433
Test: Built and boot pgagnostic targets
Flag: EXEMPT bugfix
Change-Id: If539f8a9f8c87650b8f618f302eee2c284d8ec79
There is an effort to generate system image with Soong, but there are
some difference in installed files between Soong defined system image
and KATI defined one. This change generates diffs between installed
files from two sources.
Bug: 346873717
Test: USE_SOONG_DEFINED_SYSTEM_IMAGE=true m -j on aosp_cf_x86_64
generated diff file.
Change-Id: I25c71f88d16a4efb873c21abe70ca9c41c6423ca
Merged-In: I25c71f88d16a4efb873c21abe70ca9c41c6423ca
This replicates previous fix for the similar issue
0bd9a626bd Increase dump-words-to-file capacity
Change-Id: Ibdd31d9a4588eefa585298cc4f01528f0027395a
Test: ABTD
Bug: 350309689
This build flag will indicate whether the target boots with 16kb kernel.
This flag will be used in pgagnostic targets and targets with
with the _16k suffix.
Define the build flag PRODUCT_BOOTS_16K
- When PRODUCT_BOOTS_16K := true, target boots with 16kb kernel.
- When PRODUCT_BOOTS_16K := false, target boots with 4kb kernel.
If the PRODUCT_BOOTS_16K is not defined, its value will be false by default.
Bug: 346868433
Test: Built Pixel 8 targets
$ source build/envsetup.sh
$ lunch husky-trunk_staging-userdebug
$ get_build_var PRODUCT_BOOTS_16K
false
Change-Id: Ifc5138dd76d2172e1c3bc2564efe91a0f83c5420
This CL adds DTBO partition to dev option OTA if the product
defined a dtbo image for 16KB kernel(indicated via
BOARD_PREBUILT_DTBOIMAGE_16KB)
Test: build with and w/o BOARD_PREBUILT_DTBOIMAGE_16KB set
Change-Id: I6e02d5bab0fccd193396c54e50ad2a9c3946c51d
Previous build breakage is fixed by aosp/3147481 , so
attempting to reland
This reverts commit 2ddbfee4ca.
Reason for revert: b/348547795
Change-Id: Ie7e6e54a6c1796acc37b43fe14692068e0ea31ca
Some MCTS modules should not be removed from CTS because they are
dependencies of both MCTS and CTS.
Add a whitelist as a short term solution.
Test: m cts EXCLUDE_MCTS=true
Bug: 349372705
BYPASS_INCLUSIVE_LANGUAGE_REASON=for mcts only
Change-Id: I26ada6da95a8b3547de9e54781b744facb121b05
