| commit | 9fd5886e2377b3832211f5dbc3b2cbfa0ceb940f | [log] [tgz] |
|---|---|---|
| author | Mohammad Samiul Islam <samiul@google.com> | Wed Jan 06 13:33:25 2021 +0000 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Fri Jan 22 20:13:32 2021 -0500 |
| tree | 5c811afec6cccc3ab954ecfb118da411646db545 | |
| parent | 3b455ea92ef7913ec022bd85beaa17ddf94d6a25 [diff] |
Create a function that can generate ApexInfo using target-files If an OTA contains compressed APEX inside it, then the device will need to allocate space on /data partition for their decompression. In order to calculate how much space the OTA process needs to allocate, the process needs more information about the APEX contained inside the OTA. In this CL, we are adding functionality to the OTA generation script that allows us to gather information about the APEX stored inside the target-file zip. However, we did not integrate the new functionality with the ota_from_target_files.py scrip yet. That will be done on follow up CL. Bug: 172911822 Test: atest releasetools_py3_test Change-Id: I2ac42018f628c2c21527b3e086be1f4e7e7247ad
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.