| commit | 31b6b9442a4d8017f283925c27dab2217fa8e558 | [log] [tgz] |
|---|---|---|
| author | Sasha Smundak <asmundak@google.com> | Mon Jul 26 18:23:40 2021 -0700 |
| committer | Sasha Smundak <asmundak@google.com> | Thu Jul 29 10:57:06 2021 -0700 |
| tree | 342224450ce04357562894a712399e8aeae06e36 | |
| parent | 72602c46872d672adebf76495a9ad01ba6e776a3 [diff] |
Add copy-files macro To allow refactoring a lot of product configuration makefiles. Bug: 190051051 Test: treehugger Change-Id: I1d22ed6f3df17fb616bd272c0d928aa1fdb9729a
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.