| commit | c9542abbbda4a0d48f84fd8b3c373c6a700ae427 | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Tue Jun 27 16:12:32 2023 +0900 |
| committer | Jooyung Han <jooyung@google.com> | Tue Jun 27 17:00:06 2023 +0900 |
| tree | e0be817be8a691bdd712f040d81fee52734782f7 | |
| parent | 2ac1f2fabc6c7e52a398ff25c159fc94fbc12434 [diff] |
Use apexd_host for host-side APEX extraction Host-side simulation of APEX activation is done by a new tool 'apexd_host'. This simplies checkvintf invocation for local builds and for target-files. For local builds, checkvintf no londer depends on $OUT/apex, a flattened view of APEXes. In fact, the build system doesn't need to install $OUT/apex. They are installed for now only for its side-effect of installing symbol files. We'd better not rely on $OUT/apex. For target-files, scanning/activating apexes are extracted and moved to the new tool. Now check_target_files_vintf is not more efficient because it doesn't copy .apex files to a temporary directory. Bug: 260358957 Bug: 288826922 Test: m (running checkvintf) # for local builds Test: m target-files-package && check_garget_files_vintf target-files.zip Test: atest releasetools_test Change-Id: Iba23f429d96f9ec31814196aa14bdbb800649218
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.