| commit | 03d53f7d2de988e1059e23d4b4eaf6a9e20c4d86 | [log] [tgz] |
|---|---|---|
| author | Joe Onorato <joeo@google.com> | Sat Aug 19 21:43:40 2023 -0700 |
| committer | Joe Onorato <joeo@google.com> | Sun Aug 20 07:40:44 2023 -0700 |
| tree | ce0abdae5156497613b890cbdaf21a4abf90975a | |
| parent | 987e6ba3f20c1a9586e82fa2d5ada197b1e483d2 [diff] |
Add a fake library that contains the minimum DeviceConfig that aconfig code needs to compile. The aconfig-generated code in the framework is added with srcjars. To get those srcjars, we still need a java_aconfig_library. This class is there to allow that to compile, even though those compiled .jar files are not actually used. Bug: 293195086 Test: m Change-Id: I34c21925fbc5912a34fea3e7796d5e0c77c9a4af
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.