| commit | 30e31142ce669666b4850fc843878f798ffbef90 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Tue Apr 09 00:12:30 2019 -0700 |
| committer | Tao Bao <tbao@google.com> | Fri Apr 12 15:26:32 2019 -0700 |
| tree | 477ef7b2682274956399f7e0b8533c35ebd630f3 | |
| parent | fc6948b588033d41df92757ee54ee53eddd06ac7 [diff] |
relesetools: Support running all the unittests with atest. All the unittests will be built into releasetools_test. One can run the tests with `atest releasetools_test` or the traditional way `test_utils.py`. The atest way is recommended, which additionally builds the required tools. With the current support in Soong, we can't pack the built tools into releasetools_test yet. So running `releasetools_test` alone in clound would fail. Follow-up CLs will address the issue in order to deploy the tests with TEST_MAPPING. Bug: 112080715 Test: `atest releasetools_test` Change-Id: Ica95517a5ab326f4e58fc57c6c2c276cfe882f3c
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.