| commit | 36d7c5666d299a3178cc72f67d43253f9e25865f | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Tue Apr 17 18:26:41 2018 -0700 |
| committer | Tao Bao <tbao@google.com> | Wed Apr 18 09:50:47 2018 -0700 |
| tree | 8a53e9483ea37796a7f698eb15a273956a1cb9ff | |
| parent | 1cd44482db83f51da9c8988b69bd8d13e3f6ba84 [diff] |
Remove the support for BRILLO_VENDOR_PARTITIONS. It was initially introduced in commit 2e735ca34ecf70f5ebdded9e550ca47f78b5e1e6, where it packs additional vendor images into target_files zip in order to generate OTAs. We can acheive the same goal with INSTALLED_RADIOIMAGE_TARGET, which is the way being actively used across all targets, including IoT (the former Brillo) targets. Bug: 78201540 Test: `m dist` with aosp_marlin-userdebug Test: Code search shows no active user of BRILLO_VENDOR_PARTITIONS. Test: `python -m unittest test_add_img_to_target_files` Change-Id: I8803d5377b5a39304a701cceafb243f9a228347d
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.