| commit | eda868679481b32556b87024aca735c8de28800b | [log] [tgz] |
|---|---|---|
| author | Lance Chang <jinwoong@google.com> | Sun Jun 09 09:54:32 2024 -0700 |
| committer | Lance Chang <jinwoong@google.com> | Sun Jun 09 13:22:58 2024 -0700 |
| tree | d8a5e888470917668eed52bd638403d57e8b202b | |
| parent | 6fd890a5e57285c958d67a3d49763120c77b34cd [diff] |
Add build number if TARGET_BUILD_APPS_WITH_BUILD_NUMBER is defined This change allows unbundled app builds to embed the build number in the version name by defining TARGET_BUILD_APPS_WITH_BUILD_NUMBER, so that APK files from a build can be easily identified. Ignore-AOSP-First: changes in topics with internal-only projects Test: manual build Bug: 340311907 Change-Id: I9a7e4f96f0d92c19d832933b5c68bd6b75ce9ce6
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.