| commit | bff7da701f65f63079a6c6c13f98495911b4059e | [log] [tgz] |
|---|---|---|
| author | Dmitrii <bankersenator@gmail.com> | Sat Jun 21 06:42:37 2025 +0000 |
| committer | micky387 <mickaelsaibi@free.fr> | Tue Aug 05 21:15:07 2025 -0400 |
| tree | b676218799d21f4a5402e9597a3fc542afaedfda | |
| parent | e43a6013b3653273c746a873d3ef9eec64da4737 [diff] |
layoutlib: Use wildcard to find device overlays The layoutlib_data.mk file uses `$(shell find ...)` to locate device-specific framework overlays for a hardcoded list of products. When a user's source tree does not contain all of these device directories, the `find` command outputs a "No such file or directory" error for each missing path, spamming the build log. Replace the `shell find` call with the idiomatic GNU Make `wildcard` function. `wildcard` correctly finds all existing files that match the patterns without generating errors for non-existent paths. This cleans up the build output and is slightly more efficient as it avoids forking a shell process. Change-Id: I2f4d6c593b073bd3955c0fd88d2cc699526e261c Signed-off-by: Dmitrii <bankersenator@gmail.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.