commit | 7f5cee09f93a2647aac90b7b66d1cf0187620821 | [log] [tgz] |
---|---|---|
author | Treehugger Robot <treehugger-gerrit@google.com> | Tue Oct 26 02:27:14 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Oct 26 02:27:14 2021 +0000 |
tree | 3cb4ef80b290f2a0a8c056e9d531b797430a36ef | |
parent | 60f9294b4e534bbda0f420996c14f912c31149bb [diff] | |
parent | 82a39a7d7085bd02ad2c3f645bffc705a1473ded [diff] |
Merge "Support -s in installmod command" am: 8cdc80bc24 am: 12f85f31e3 am: e7af6fa1e6 am: 493776ffd7 am: 82a39a7d70 Original change: https://android-review.googlesource.com/c/platform/build/+/1869665 Change-Id: Ia6ce242ae4012af90def209d8c6fe5d4cf78809c
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.