commit | 880933574060df1ec643eb2b7304d1ae7893999d | [log] [tgz] |
---|---|---|
author | Ian Kasprzak <iankaz@google.com> | Wed Sep 04 19:02:43 2019 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Wed Sep 04 19:02:43 2019 -0700 |
tree | 5bbd29ca610ad4a469ac23be89416e0eacf34751 | |
parent | b2f1cfbd4038e73007570875fefc7b65ae64366d [diff] | |
parent | 40448f262ee377d2ef74506c615ff598336e94b4 [diff] |
Merge "Revert "Moving GSI-specific files to system_ext"" am: 414108c6c1 am: b5195f128d am: c1b6e703a9 am: 303eaac2c0 am: 40448f262e Change-Id: I75810255c2523e38fb35506b222b425198018139
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.