b51e1ffce4
This should not be necessary because bp2build should emit a package() statement with default_visibility = public. However, there appears to be a problem with bp2build's symlink forest, where it doesn't handle symlinks correctly. build/target is a symlink to build/make/target, but in the symlink forest, build/target is a symlink to the source dir's build/target instead of to the symlink forest's build/make/target. This means that when reading this build file via the build/target symlink, you won't get the bp2build-provided default visibility. (or any other bp2build generated targets) We should send a proper fix for this, but in the meantime submit this quick fix to resolve some failing builds. Bug: 269577299 Test: lunch bertha_x86_64-userdebug, m nothing Change-Id: Ia45c7f4a0655b1364b735d6eccf25cad70cad134
Android Make Build System
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.