| commit | f88e0ce01d4c9bf4751aec277437981ea4239f42 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Mon Mar 18 14:01:38 2019 -0700 |
| committer | Tao Bao <tbao@google.com> | Mon Mar 18 21:01:43 2019 -0700 |
| tree | 2ff1f525602c3aef1266f337010de5e3dcc5e1c5 | |
| parent | 0573298a182fc673cfee1c89e183b515c5383d0d [diff] |
releasetools: Kill the use of os.getenv('AVBTOOL').
OTA tools should pick up the avbtool, as listed in dict['avb_avbtool'],
from the current PATH (plus bin/ under the dir specified via `--path`),
the same way as handling all other host tools.
Test: `m dist`
Change-Id: I3eb4d2c61979b03d9c23b2403d9a38cf052d87ea
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.