| commit | 42131496c8ad11e11ab265a4cdf6a5f2c5522534 | [log] [tgz] |
|---|---|---|
| author | Bowgo Tsai <bowgotsai@google.com> | Wed Mar 31 10:56:28 2021 +0800 |
| committer | Bowgo Tsai <bowgotsai@google.com> | Wed Mar 31 03:11:14 2021 +0000 |
| tree | 28c7bf05a5afe4cba4f0d407996c09f99d238657 | |
| parent | a0e69fc900463873de5f197670a3660507c90948 [diff] |
Adding bootimage_test_harness artifact to droidcore Currently bootimage_test_harness is only built on a few targets on release branches. However, we might have a last minute build breakage on release branches as bootimage_test_harness is not built on dev branches. Moving it to droidcore so we can have more completed build coverage on pre-submit/post-submit builds. Bug: 183865297 Test: `make` then check $OUT Change-Id: I496609401a9444706726256d2f7b45c6bb69ee94
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.