| commit | cf821fc963fa74e4875d5d305e24492d9c945044 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Mon Jun 24 12:39:10 2019 -0700 |
| committer | Tao Bao <tbao@google.com> | Mon Jun 24 14:08:36 2019 -0700 |
| tree | 4456fcb67f6fb8bb863c326a1cfe808438af4ecc | |
| parent | f26a4e459ec578778592c45a31c7a5c5df1caad7 [diff] |
Fix an issue in setting up PATH. `PATH=$(foreach p,$(INTERNAL_USERIMAGES_BINARY_PATHS),$(p):)$$PATH` will produce a space separated string due to `foreach`, if $(INTERNAL_USERIMAGES_BINARY_PATHS) has more than one string. We didn't hit the issue in the past because $(INTERNAL_USERIMAGES_BINARY_PATHS) had contained only one path in practice. Test: TreeHugger Change-Id: I74ef4356668af63d871a81f6bfd4c9324aa1d956
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.