| commit | 6b795dc6a5e6f479adae456b978ba1d2bc761dae | [log] [tgz] |
|---|---|---|
| author | Sasha Smundak <asmundak@google.com> | Wed Aug 18 16:32:19 2021 -0700 |
| committer | Sasha Smundak <asmundak@google.com> | Thu Aug 19 13:54:53 2021 -0700 |
| tree | f1ad2e79afae160aca29be5a4d745c5962ee5d48 | |
| parent | bb0d6a42d8aa792da173f4a7cf074b0c47fb5478 [diff] |
Add find_files builtin, use it to fix find_and_copy implementation The macro find-and-copy finds all the files in the given source tree that match the given filename patten and create <source>:<dest> pair with the same relative path in the destination tree. Bug: 193540681 Test: rbcrun build/make/tests/run.rbc Change-Id: Ic4315ce2fab7a7791ab55dd9eed039205a1c721a
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.