| commit | 11f188c09ae2cd0446296f8bcf996f2e63f3a0e0 | [log] [tgz] |
|---|---|---|
| author | Saagar Jha <saagarjha@google.com> | Thu Jul 13 23:31:59 2023 +0000 |
| committer | Saagar Jha <saagarjha@google.com> | Thu Jul 13 23:36:29 2023 +0000 |
| tree | d7ecb60ddf529bed28080b06701a4be3db78a790 | |
| parent | e75c063d1f3ff46468c88ca9788f8bbbfbff46cc [diff] |
Use command instead of which to locate/run adb If adb is not found on PATH, which will silently fail and evaluate to the empty string. This will cause the remaining arguments to be interpreted as a command to run in the shell, which is generally undesirable. (Consider, for example, "adb reboot" -> "reboot".) Bug: 24473359 Test: Just run adb before lunch so it's not on PATH Change-Id: I6b20722add6c67d1d2627f963dc66095502ab816 Signed-off-by: Saagar Jha <saagarjha@google.com>
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.