| commit | a8a5a3ff625cd3a65a916767c950635b12a7b81b | [log] [tgz] |
|---|---|---|
| author | Justin Yun <justinyun@google.com> | Thu Jun 15 23:11:03 2023 +0900 |
| committer | Justin Yun <justinyun@google.com> | Fri Jun 16 00:10:33 2023 +0900 |
| tree | 637e5593f7f3aea2244c3a6554b40e430fae5bbd | |
| parent | 1cda03b44bb061c79d4c449a75f6d7d667d0b50e [diff] |
Use map_file_generator only for the supported file systems map_file_generator can generate map files from erofs and ext# file systems. Check the file system type and copy images and generate map files if supported. Otherwise skip these steps. If the image files are not copied, add_img_to_target_files will generate the image files and map files. Bug: 286870582 Test: lunch bertha_x86_64-userdebug && m dist Change-Id: Ib92dd989cf61b1e376107a507eae9222ceb1d0d4
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.