| commit | 5217eed7a305042adc0560e336ef95c02d6031d1 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Thu Nov 08 08:09:54 2018 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Wed Nov 14 07:53:23 2018 +0900 |
| tree | 01fa0ebf8616db6e7ba2f1e0d43410f3271f6015 | |
| parent | f41d24acb3d053613f8f84fb26b9af7e10b5dcb8 [diff] |
Add TARGET_FLATTEN_APEX TARGET_FLATTEN_APEX, when set to true, flattens APEXes that are on /system. Flattening an APEX means files in it are not packaged as a mini file system image, but exist in the /system partition as individual files. This option is for devices where kernel does not support loopback devices or the maximum number of loopback devices is too small (though the threshold is TBD as of now). Bug: 118485880 Test: TARGET_FLATTEN_APEX=true m apex.test; tree out/target/product/.../system/apex/apex.test shows list of files in it. Test; m apex.test, then a file out/target/product/.../system/apex/apex .test.apex exists. Change-Id: Ie13cb062c1387d55689692ba2b123e606ada8aa4
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.