Fix include-what-you-use for Go modules in build/make (part 2) Soong was incorrectly passing -I arguments to `go compile` for all transitive dependency packages, allowing `import` statements to reference packages that were not listed as dependencies of the module in the Android.bp file. This bypassed Soong's visiblity restrictiions. Add direct dependencies on any packages referenced by `import` statements. Bug: 439627342 Test: builds with transitive dependencies removed from -I flags to go compile Change-Id: I089e5069153667714d5a61506c6ff3ebfae0a6f1
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.