| commit | 8b674819acc11adfe8895db864971e80c1a5083d | [log] [tgz] |
|---|---|---|
| author | Yo Chiang <yochiang@google.com> | Fri Sep 20 15:59:13 2019 +0800 |
| committer | Yo Chiang <yochiang@google.com> | Sat Oct 05 11:35:33 2019 +0800 |
| tree | 4dcb13f16462b992b651ae4fab8a5dfae3cd03b9 | |
| parent | 491966fb7fdd32a98eed84190a57cc0a2511acf7 [diff] |
Add x86 / x86_arm mainline_system product - Add mainline_x86 / mainline_x86_arm board - Add mainline_system_x86 / mainline_system_x86_arm product - BOARD_SYSTEM_EXTIMAGE_FILE_SYSTEM_TYPE := ext4 These products build only system.img and vbmeta.img. These serve as a "golden example" for x86 / arm64 CSI. Bug: 141972143 Bug: 141657175 Test: lunch mainline_system_x86-userdebug; m Test: Compare $ANDROID_PRODUCT_OUT against sdk_phone_x86 / aosp_cf_x86_phone Change-Id: I40dec69ceadfe7057c1706b883b81958d3c0a416
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.