commit | 8e28a17bfef9272879a026fb4e30b87413f107e6 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Mon Dec 30 22:08:07 2019 -0800 |
committer | Colin Cross <ccross@android.com> | Mon Dec 30 22:08:07 2019 -0800 |
tree | fd34dc640ccdf2e5f6d20219fdb10052e11210ed | |
parent | 4506b17dd3c28179f25b8689503e79149732d387 [diff] |
Add Soong android_app and android_test modules to javac-check android_app and android_test modules were not built as part of javac-check, which resulted in not running them in the Error Prone build. Fixes: 146455923 Test: m RUN_ERROR_PRONE=true javac-check Change-Id: I278d7ee0cdc3f49aa8fa4d4f13309e29d700f2ba
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.