commit | c9a5d76f32371df645b9332f4cc5048e95ea3b8b | [log] [tgz] |
---|---|---|
author | Anton Hansson <hansson@google.com> | Tue Jun 14 11:56:30 2022 +0000 |
committer | Anton Hansson <hansson@google.com> | Wed Jun 15 17:59:49 2022 +0000 |
tree | f271984cae8c09b4dcd7d4f0ce4758033004c27a | |
parent | d02946c4c378d5838afe8c43654a7d8f9d6c7a37 [diff] |
Don't exclude docs build from using prebuilts Even though it doesn't have google modules in PRODUCT_PACKAGES, the docs build wants to use prebuilts when the rest of the branch does. Bug: 230478310 Test: m docs (inspect MODULE_BUILD_FROM_SOURCE) Merged-In: I1d67f4099e9fdc5fbaeeb0bf0fce80aa91c05eb5 Change-Id: I1d67f4099e9fdc5fbaeeb0bf0fce80aa91c05eb5
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.