| commit | fb10840da5e5bb3ee94bb81f7e000d58cded2c60 | [log] [tgz] |
|---|---|---|
| author | Mårten Kongstad <amhk@google.com> | Wed Sep 13 10:15:01 2023 +0200 |
| committer | Mårten Kongstad <amhk@google.com> | Wed Sep 13 10:15:01 2023 +0200 |
| tree | dc194e0ec9cc3c15b5f509e1643aa2e4a3324828 | |
| parent | be6ba681e9f6e78e3cc79f1f0a9a4589c3c0c9d9 [diff] |
aconfig: explicitly @hide FLAG_ constants Because of a bug in metalava [1], the flag constants are incorrectly considered not-hidden when metalava generates the API signature files. This means the FLAG_ constant name will be used, instead of the FLAG_ constant value, which is what we want. While waiting for b/300211291 to be fixed, explicitly mark the FLAG_ constants as hidden (and keep marking the classes as such). This CL can be reverted when b/300211291 is fixed. 1. Item.isHiddenOrRemoved does not check if its parent item is hidden, tracked in b/300211291 Bug: 297881670 Test: atest aconfig.test aconfig.test.java Change-Id: I05de8344ccb424bee51c39f9609489ad312397ce
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.