commit | ece054c856fa083a343ac13be6e286c6da3853f3 | [log] [tgz] |
---|---|---|
author | Mårten Kongstad <amhk@google.com> | Thu May 02 09:45:11 2024 +0200 |
committer | Mårten Kongstad <amhk@google.com> | Thu May 02 09:50:33 2024 +0200 |
tree | 06f039666770a4dd3e80ad76cce72250bc03d20d | |
parent | 7faf630b7c814ff3590d1cbaf55ed70f019f396e [diff] |
check-flagged-apis: change internal format Switch the internal format to represent Symbols to (something close to) the format described in section 4.3.2 of the JVM spec, i.e. com/android/SomeClass/someMethod(II[Ljava/lang/String;)Z This will make parsing method parameters from api-versions.xml easier, as that file already uses this format, and converting API signature files to the same format is less painful than going in the other direction. Bug: 334870672 Test: atest --host check-flagged-apis-test Change-Id: I1e1fb8fe208cd51cce2cc129f5aa1cb495672c16
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.