| commit | 34ea73940e0bebb9c166856dbcebafd14b7348dc | [log] [tgz] |
|---|---|---|
| author | Robin Lee <rgl@google.com> | Thu Jan 02 20:21:18 2020 +0100 |
| committer | Robin Lee <rgl@google.com> | Thu Jan 02 19:25:20 2020 +0000 |
| tree | 6263e4029ae03c4165f123ea5cd7d78f77d5017e | |
| parent | 4506b17dd3c28179f25b8689503e79149732d387 [diff] |
Go one directory up looking for releasetools path Change I366099c3dfd5fa4282745ef258a8cf35338e1e42 introduced a more restricted search where we only look in out/host/x/bin instead of out/host/x when looking for files. Because signapk is in out/host/x/framework, and lib64 is in out/host/x, we need to go one level up for this to work properly. Fix: 147096688 Test: atest --host releasetools_test releasetools_py3_test Change-Id: I597e1d95c09eb0e27b2faebb107218761901d9ac
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.