| commit | 2495360637b126da31f29330dfacd9b4b1a710a3 | [log] [tgz] |
|---|---|---|
| author | Treehugger Robot <treehugger-gerrit@google.com> | Wed Nov 24 20:35:52 2021 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Nov 24 20:35:52 2021 +0000 |
| tree | 3e748e685694ba8c0833f6cad49933e2f5c9c3d8 | |
| parent | fc05da88f546cef242a99cbc9f53b9cbc4c39e31 [diff] | |
| parent | fd8a495fff65f674185f549dc86bfe0d08b29004 [diff] |
Merge "Ensure there are no empty paths in ANDROID_BUILD_PATHS and PATH." am: 46bd6ec0f6 am: 1ec033c132 am: 8676adc660 am: fd8a495fff Original change: https://android-review.googlesource.com/c/platform/build/+/1900564 Change-Id: I5557c20f12bb9d17c9a09ee4b1a325bcd66f0515
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.