| commit | b0df4fe415a07550d083693110bfe8b47e3d8ed3 | [log] [tgz] |
|---|---|---|
| author | Shareef Ali <shareefalis@cyanogenmod.org> | Tue May 28 22:44:31 2013 -0500 |
| committer | Jackeagle <jackeagle102@gmail.com> | Sat Dec 12 07:21:28 2020 +0100 |
| tree | 9225a273531caa169890004de504c371d35a0320 | |
| parent | 8dcf6bb1173408e914d69cda09a65efbfe284db5 [diff] |
build: get rid of the sparse expand stuff * i don't see a reason why we are doing this because we never deal with flashing system img rawly * This will put useless write on ssd.. * we don't have space on ssd Change-Id: Icd53d161b8515f5eca238b98ad68515d69caa34f
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.