commit | 93eee510f9653020f83653e0d15a53cc15b83144 | [log] [tgz] |
---|---|---|
author | Karsten Tausche <karsten@fairphone.com> | Wed May 10 14:30:21 2023 +0200 |
committer | Prashantsinh Parmar <prashantsinh.parmar@fairphone.partners> | Mon Dec 18 16:42:27 2023 +0100 |
tree | 366d936503330e9f741d45e05ecf0d8e6e299d3a | |
parent | 2fe8613466a54f56a9618028cc720f0689f50f85 [diff] |
Set ro.build.version.base_os for SMR on 4.A.0022.0 Issue: FP3-A11#476 Issue: FP3-A11#474 Issue: FP3-A11#472 Issue: FP3-A11#467 Change-Id: I3df7b9444915f98836100adcc4ac6419fb3ba465 (cherry picked from commit 7061b6422ec94d5a6ac78b77ce412502d2897247) (cherry picked from commit 71b7b55bc5da65b819a89971c9f6b76f8300ebc8) (cherry picked from commit 6c9f58ed19fc5c8e7a734483326a2e55a2eb3516)
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.