commit | 1b5883390691e66affc61cf9c5ba4dae583fcb46 | [log] [tgz] |
---|---|---|
author | Spandan Das <spandandas@google.com> | Mon Apr 08 17:45:26 2024 +0000 |
committer | Spandan Das <spandandas@google.com> | Tue Apr 09 00:20:22 2024 +0000 |
tree | d606d40a315a4f42ad20bd4b690e860368bbb051 | |
parent | 307224c7d4b600ccc16f7aa19154ab218988f972 [diff] |
Drop HOST_CROSS_OS special-case in source vs prebuilt mainline selection We currently do not have many products that cross compile to linux_bionic, and none of them use google apexes. One exception is `mainline_sdk` product, but this product exclusively builds using the `mainline` release config. This release config contains the necessary RELEASE_APEX_CONTRIBUTIONS_* to provide sources during the build, so we do not need this additional special-case here Bug: 308188056 Test: lunch trout_arm64-next-userdebug && get_build_var PRODUCT_PACKAGES; verified that google apexes do not appear there before this CL, effectively making this CL a no-op for that product Change-Id: Ibfdc742b6ae01242be22a3d3f6bb3c0cf551705f
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.