commit | 5771e8cbf1e33b194a3d0856298726d1a9801c21 | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Fri Aug 31 15:59:23 2018 -0700 |
committer | Dan Willemsen <dwillemsen@google.com> | Fri Aug 31 15:59:23 2018 -0700 |
tree | 8238564b2ae58813de8dcd29c1b45767e240379c | |
parent | 3e9e6af0ff58c4003c245eacffb7ee2ddcc3fa6a [diff] |
Switch protoc javastream plugin to using explicit path The previous PATH=$PATH:out/... logic was incorrect, since the version in $PATH would override the one out. And now that we're limiting what's accessible via $PATH, that caused an error. Instead, ensure that all protoc plugins are specified explicitly with --plugin, then remove the PATH modification. Test: cd frameworks/base/cmds/am; mma (with protoc-gen-javastream in $PATH) Change-Id: I6690727504f67f84fdc95ed93eabdf3351e5cb0b
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.