| commit | f07f721235e9f074cdb7c470ad52d2f240d4e706 | [log] [tgz] |
|---|---|---|
| author | Yoshisato Yanagisawa <yyanagisawa@google.com> | Thu Jan 10 13:58:33 2019 +0900 |
| committer | Yoshisato Yanagisawa <yyanagisawa@google.com> | Thu Jan 10 14:29:45 2019 +0900 |
| tree | f05c4c6d0a8b5eb0c0081ae614f4295e44b01ade | |
| parent | eeeb9f96c8995c6c8213cb13a790296281291665 [diff] |
Remove code to start Goma compiler_proxy. Since the code to start compiler proxy is implemented in soong now (https://android-review.googlesource.com/c/platform/build/soong/+/839293). We do not need to do that in goma.mk. Bug: 118390303 Test: After staring goma client, executed followings: Test: USE_GOMA=true make -j 4 Change-Id: If3da9908483e183f539c0d6ef9dc5826200b0d6b Signed-off-by: Yoshisato Yanagisawa <yyanagisawa@google.com>
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.