| commit | e3b44f551c286561a1f7a9f38c51d182e76d4542 | [log] [tgz] |
|---|---|---|
| author | Po-Chien Hsueh <pchsueh@google.com> | Wed Sep 30 14:37:40 2020 +0800 |
| committer | Po-Chien Hsueh <pchsueh@google.com> | Wed Sep 30 08:18:03 2020 +0000 |
| tree | 75854c3b74036773ebeded92ebc920d397ac48c7 | |
| parent | fd4a406174341648fafbe017960fe0d7de2e9e15 [diff] |
Filter out host paths on platform-availability-check errors If a module, which is installed to both the host and the platform, fails the platform-availability-check, the build system might use the host install path to report errors. Filter out the host install path so that the platform install path is used. Bug: 169393514 Test: make Change-Id: Ib39715ffc45cc32e3bd7ce5f2a3725d243f3237f
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.