| commit | 5e143bacf8d3377a0ee043f77f336fb6dfcfc8c0 | [log] [tgz] |
|---|---|---|
| author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Jan 13 23:27:26 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Jan 13 23:27:26 2020 +0000 |
| tree | 8f5299bf883ee97d1fa121b2a0aee60db0373a30 | |
| parent | 96e760f4374eea4aeadc55f52e90923705c4d754 [diff] | |
| parent | 4c84dea09e4e21f70e8c4b3f26d8316641b267c3 [diff] |
Merge "Make allmod() and pathmod() py3 compatible" am: 5740e22d7c am: 3e3a93ca25 am: 4c84dea09e Change-Id: Ia91b0d170f1fbbd15df750d07d56d6e7da77929a
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.