| commit | c8e1d69687580185691542df01e2a9ba301f27a7 | [log] [tgz] |
|---|---|---|
| author | Jihoon Kang <jihoonkang@google.com> | Sat Jun 24 00:18:12 2023 +0000 |
| committer | Jihoon Kang <jihoonkang@google.com> | Tue Jun 27 04:46:50 2023 +0000 |
| tree | f450d8f2e2fa8ea545ecad6e2c627b56a9ca9491 | |
| parent | 9448754144e407576462df6faa1dfe9e9346506f [diff] |
Add --classes optional flag in list_files The flag enables list_files to output a list of .class files pattern that will be generated when compiling the java files in the input directory. The flag can be used to extract the appropriate class files from stub jar file provided via dep_api_srcs in per api scope sdk_library generated java_api_library modules. Test: m --build-from-text-stub in same topic Bug: 275570206 Change-Id: I134fcd9781024dcb6781297d02645f5fb9befb18
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.