commit | 1a88cffd42d536f3da84c84eb7d5d6d45a705bdc | [log] [tgz] |
---|---|---|
author | Jihoon Kang <jihoonkang@google.com> | Wed Oct 23 20:52:40 2024 +0000 |
committer | Jihoon Kang <jihoonkang@google.com> | Wed Oct 23 22:16:20 2024 +0000 |
tree | a1b1a3933686f2490697e4bbebd328200deb7176 | |
parent | d9e5a2ea27cc0164d4f7bfda637c2113b4c5ae95 [diff] |
Export PRODUCT_COPY_FILES to Soong PRODUCT_COPY_FILES entries are used to auto generate the prebuilt_* modules in filesystem_creator. Test: m nothing Bug: 375053752 Change-Id: I7ed49645d9ab11f6b57f257b5741a855ac86c688
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.