| commit | af81e20653acdead85ba407bd1dbf7df6c984e73 | [log] [tgz] |
|---|---|---|
| author | Zhi Dou <zhidou@google.com> | Wed Jun 14 20:38:20 2023 +0000 |
| committer | Zhi Dou <zhidou@google.com> | Fri Jun 16 12:40:40 2023 +0000 |
| tree | ccfaede8e3252fcb9ca4426d907f3d0791ad1b90 | |
| parent | e4635b3e04b8f2b8248adc4efb16e4cd99259391 [diff] |
aconfig: change java flag method name to camelCase Before java code will directly use the flag name as the method name. This change adds funciton to try the best to convert flag name to camelCase, and then use the camelCase string as the method name in the generated code. Bug: 279483816 Test: atest aconfig.test aconfig.test.java Change-Id: I45fc6df46c9d535cd38a657a41313202f9b660af
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.