| commit | a1d6109978e0df6daab08b75707e06fcc23913c5 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Tue Feb 21 11:36:20 2023 -0800 |
| committer | Colin Cross <ccross@android.com> | Mon Feb 27 21:12:07 2023 +0000 |
| tree | bacf48cf4d1f687262826a66a52a993e12061ea7 | |
| parent | 2e39131d8075b78bd9db956effb43312a19524c1 [diff] |
Disable riscv64 dependency on bcc and ld.mc riscv64 can't build the device version of bcc and ld.mc due to a dependency on an old version of LLVM, but they are listed in base_system.mk which can't add them conditionally based on the target architecture. Add a hack to base_system.mk to silence the warning that the host-only modules are listed in PRODUCT_PACKAGES. This can be removed once renderscript is removed from the platform. Test: lunch aosp_riscv64-userdebug && m Change-Id: I8efd769a34b110dfb838f7016e029369cb9a0f01
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.