| commit | 59c61acf6403abe172fba264366530c94fd0111b | [log] [tgz] |
|---|---|---|
| author | Jihoon Kang <jihoonkang@google.com> | Wed Nov 15 00:38:41 2023 +0000 |
| committer | Jihoon Kang <jihoonkang@google.com> | Wed Nov 15 00:38:41 2023 +0000 |
| tree | 22507e84e7e473c05715d37d46c0b46255143d41 | |
| parent | 534b47bc8e2942d7b85652cca7495c2051ec1343 [diff] |
Set BUILD_FROM_SOURCE_STUB=true for finalization Build from text stub feature was initially implemented to improve build performance and may be unstable for api finalization, as the stubs generated from api signature files miss some methods, which may cause backward compatibility issues. Therefore, this change disables building from text stub for api finalization. Test: build/tools/finalization/finalize-aidl-vndk-sdk-resources.sh and inspect generated ninja file to verify that the stubs are generated from source Java files. Bug: 310279899 Change-Id: I9d374e973788bc97514815f64eeb949a94a97647
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.