| commit | cb559ac3d89db720bb2df2f2899c2a8bed2547db | [log] [tgz] |
|---|---|---|
| author | Yo Chiang <yochiang@google.com> | Thu Sep 19 10:15:10 2019 +0800 |
| committer | Yo Chiang <yochiang@google.com> | Tue May 26 14:09:25 2020 +0000 |
| tree | 0aad6b420755d0a539030f5944743cda9ffe24c3 | |
| parent | 0e19b741120f121eaa3356ed282fb55d79abe224 [diff] |
Remove mainline_arm64.mk mainline_arm64 is broken for quite some time. Let's just remove it rather than trying to fix it. IIUC this was a testing ground for mainline_system.mk when it was first introduced. Now we have plenty of products that use mainline_system.mk (e.g. mainline_system_arm64, aosp_arm64, aosp_<pixel>, ...). Bug: 141443017 Test: TH Change-Id: I8e0825b2d94134fd8e9e3edc5e2aa15dbcdf10ba Merged-In: I08990b70d45c0663a9700f41b670513674bf7e97
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.