| commit | 727dd6c4e5aa07149a8c98ece8ba116beca1fff3 | [log] [tgz] |
|---|---|---|
| author | Jihoon Kang <jihoonkang@google.com> | Thu Feb 22 20:33:38 2024 +0000 |
| committer | Jihoon Kang <jihoonkang@google.com> | Thu Feb 22 20:39:47 2024 +0000 |
| tree | 35d45ea33acc48ae55a38201a9d963aed6a56f2e | |
| parent | 49f08d9328f83d32540038a42b5c14d9413af430 [diff] |
Introduce the product sdk_with_runtime_apis This product is an extension of the sdk product, and allows the "runtime" api stub artifacts are exported to the dist directory and used to generate the stubs. Test: lunch sdk_with_runtime_apis-trunk_staging-eng && m sdk dist Bug: 326312949 Change-Id: I96f6c1f5a5e7b40165d55ea4c0898a880ed62c96
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.