| commit | 8722201866e3ad145b755953e84afa057349dd8a | [log] [tgz] |
|---|---|---|
| author | Nikita Putikhin <nputikhin@google.com> | Tue Jul 16 12:37:59 2024 +0200 |
| committer | Nikita Putikhin <nputikhin@google.com> | Tue Jul 16 12:41:19 2024 +0000 |
| tree | a9a6e9c4c15f2a8f22ba5a9145bf89d84fb03ddf | |
| parent | c067bcb19f79b1adb0f985920a7ef94fce73eee5 [diff] |
Use test install base template instead of a hardcoded path ** 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
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.