commit | dfbfcbfca505fb14bf85d66fd17450769d36e1bb | [log] [tgz] |
---|---|---|
author | Anton Hansson <[email protected]> | Thu Mar 10 18:31:17 2022 +0000 |
committer | Anton Hansson <[email protected]> | Thu Mar 10 18:35:18 2022 +0000 |
tree | 7fb3d65b588414a64b32e4448eb5da8d2a9d6376 | |
parent | 542aeac378e77e984bfac4f2df84b59f87860ce7 [diff] |
Convert extension version assignment to be simple To match what was done in I4798fb69c639e6d52d275a5b793fa0c8ba876202. Test: m nothing Merged-In: I4798fb69c639e6d52d275a5b793fa0c8ba876202 Change-Id: I65b7c5974e0ce64bb43474e49ef9ed8d2b13d001
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.