commit | 25478181b928a54f7f11a3917f38cf1667b442fb | [log] [tgz] |
---|---|---|
author | Daniel Mentz <danielmentz@google.com> | Wed Aug 21 18:09:46 2019 -0700 |
committer | Daniel Mentz <danielmentz@google.com> | Mon Aug 26 18:17:14 2019 +0000 |
tree | 80991aae9c465fd47880c3a17b87389537c35860 | |
parent | bca3111cfa51943f95dbcf0b8bda6f923afeaea3 [diff] |
Consider search_path to locate avb_*_key_path files avb_*_key_path are usually relative file paths. If these files cannot be located from the current directory, try prepending OPTIONS.search_path. Bug: 139836256 Test: python -m unittest test_common Test: python -m unittest test_add_img_to_target_files Change-Id: I020b257f458a1f5762691d0499feaf4027e37126
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.