| commit | 25d1d97ceb99481019629798648548fb05793ecb | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Tue Dec 18 12:09:51 2018 -0800 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Dec 18 12:09:51 2018 -0800 |
| tree | 6c8e5c2cb8c2876afece633311274f538f051d67 | |
| parent | 72118c5221ca3bdeb2f8366687f9f7de462ce75b [diff] | |
| parent | c8dd0b6eac3c42b21523dc4c5d34485743fa6454 [diff] |
[automerger skipped] Merge "Allow mainline_arm64 to have product contents" am: 632ee3dee8 am: 0fdc4adae9 am: c8dd0b6eac -s ours Change-Id: I6ee2baf5cac6224278d498bb92a540b7fa8fed1c
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.