The PRODUCT_DISABLE_SCUDO only removes scudo from the list of
sanitizers. It doesn't change the allocator to be used.
Instead use MALLOC_LOW_MEMORY := true, which causes a device
to use a low memory version of the allocator.
Bug: 318756974
Test: Treehugger.
Change-Id: Idaf57cfa4fa723ce8d7f285b2bad8ec29059f0df
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
Note that the namespace is "libbinder".
Bug: 333854840
Test: N/A
Flag: RELEASE_LIBBINDER_CLIENT_CACHE
Change-Id: Iecfb62c14685afcce72cf89ad61536efd2d17e31
`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 is currently not the default behavior. products opt-in by
setting ro.cp_system_other_odex=1 (with cuttlefish being the only
product family in internal main that sets this).
With https://r.android.com/3144182, the odex files of system_ext and
product are now installed in system_other. Since the odex files are not
copied to /data, it triggers dexopt on device, which slows down first
boot performance.
This CL changes makes cp_system_other_odex=1 in
build/make/target/product/runtime_libart.mk. This file is inherited by
internal google products and external OEMs, and ensures that the odex
files are copied from system_other to /data/dalvik-cache on first boot.
Test: lunch oriole-trunk_staging-userdebug && get_build_var
PRODUCT_VENDOR_PROPERTIES # verified that this property is set
Test: In logcat, found the following match for `CalendarGooglePrebuilt`
(a /product app)
```
Successfully loaded /data/dalvik-cache/arm64/product@app@CalendarGooglePrebuilt@CalendarGooglePrebuilt.apk@classes.dex with executable: 0
/data/dalvik-cache/arm64/product@app@CalendarGooglePrebuilt@CalendarGooglePrebuilt.apk@classes.dex is kOatUpToDate with filter verify
Dexopt result: [packageName = com.google.android.calendar] DexContainerFileDexoptResult{dexContainerFile=/product/app/CalendarGooglePrebuilt/CalendarGooglePrebuilt.apk, primaryAbi=true, abi=arm64-v8a, actualCompilerFilter=verify, status=SKIPPED, dex2oatWallTimeMillis=0, dex2oatCpuTimeMillis=0, sizeBytes=0, sizeBeforeBytes=0, extendedStatusFlags=[]}
```
Bug: 349083274
Bug: 343367700
Change-Id: I42eda6742adcce7caccb1f2302578c01df8a24fd
** 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
The `MethodItem` type represents both a normal method as well as being
the super type of `ConstructorItem`. That organization causes a number
of issues in Metalava and has lead to quite a few issues where code
that only expected to be run on methods and not constructors was run on
both. So, a new type `CallableItem` has been added that will eventually
become the super type of both `MethodItem` and `ConstructorItem` and
`ConstructorItem` will no longer extend `MethodItem`.
This change prepares this code for that change by overriding
`visitCallable(CallableItem)` instead of `visitMethod(MethodItem)`
because the latter is only called for methods not constructors.
Bug: 352481366
Test: atest check-flagged-apis-test
Change-Id: I3039bc0154b00ca57cb48c7447c5901b991b57e5
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
system.img is built from both $OUT/system and $OUT/root. As the diff
tool doesn't check $OUT/root, this change temporarily adds two files
under root (adb_keys and init.environ.rc) to allowlist. They will be
removed once the diff tool is fixed.
Bug: 351258461
Test: build
Change-Id: I0f24dcae67c72be5619a86f6f025ec8bcb146084
This change adds code in java code to read from new storage. However the
generated code won't geneerate code contains code for new storage, since
the build system won't pass `allow-instrumentation` to java codegen.
Test: atest aconfig.test.java
Bug: 349874828
Change-Id: I70983fa97de6633f467d968109d134d46f895a89
Wear APIs are currently not being included in sdk builds, since Wear
flags are not part of the default set of flags read by the build system.
To mitigate this, we are explicitly including Wear flags in the list of
flags processed for sdk builds.
Bug: 350775600
Test: sdk builds contain Wear flags
Change-Id: I9e78a7f4282fa80a2ea30cbbc358c8e45ced0a9e
* changes:
[automerger skipped] Merge "RESTRICT AUTOMERGE: Exclude mcts tests from cts based on the env config, a CP from aosp/3081046." into android14-tests-dev am: 560eb19582 -s ours
[automerger skipped] RESTRICT AUTOMERGE: Exclude mcts tests from cts based on the env config, a CP from aosp/3081046. am: b60ebe0d7f -s ours
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
This reverts commit 70b9ac0ddd.
Reason for revert: Droidmonitor created revert due to build breakages in b/352582602.
Change-Id: I8a8e38ccf3e715e9b4746ac333aed0cc13d11969
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
