commit | a64ebbdad3d5443db8a9926b3ee679fc17d8b3ba | [log] [tgz] |
---|---|---|
author | Lee Shombert <shombert@google.com> | Thu Mar 21 16:08:50 2024 -0700 |
committer | Lee Shombert <shombert@google.com> | Thu Mar 21 16:08:50 2024 -0700 |
tree | 1a0cc538a4c88e1ef26b57e75519a8ae9b2fbd09 | |
parent | 6d5a509efa35199f1903caebe560fe3ca9f63f6f [diff] |
Export the sqlite build flag to more products sqlite is used in many products, including the Android system, mainline modules, and sdks. The trunk-stable build flag must be exported to all of these targets. Bug: 323176655 Change-Id: I23480610b710c0ec3e49c364c179ea76297fb494
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.