envsetup: Optimize vendorsetup.sh scanning Follow up to: ag/38202271 Previously, source_vendorsetup captured the output of `find` into a variable and iterated over it using a standard `for` loop. This approach is unsafe because the shell splits the variable expansion on whitespace, causing errors if any directory or filename in the tree contains spaces. I missed this issue because my checkout did not contain such files, and I assumed this won't happen. But clearly I was wrong, because some users immediately began reporting problems. This change switches the iteration logic to use a `while IFS= read -r` loop with process substitution. This ensures that paths with spaces are handled correctly and avoids potential issues with variable size limits if the list of vendor setup files is large. This is a good change regardless because it's safer and more technically correct. Fixes: 481832043 Change-Id: Iac3b1e36bd775267333c23ad5c294f8df41331ae
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.