commit | 6284936f20f564ced4989d7b35974d492859b3c9 | [log] [tgz] |
---|---|---|
author | Wei Li <weiwli@google.com> | Mon May 15 15:11:43 2023 -0700 |
committer | Wei Li <weiwli@google.com> | Tue May 23 23:12:36 2023 +0000 |
tree | 0b4e1abdc12506f544f3bd03514bc54cbe675c3e | |
parent | a75b82f9d240a3e9c49076cc9025b627591e634d [diff] |
Add upstream package of a prebuilt fork package, which will have the package information from the METADATA file. Bug: 266726655 Test: CIs Test: lunch barbet-user && m sbom (cherry picked from https://android-review.googlesource.com/q/commit:16e7aa3c2ea779ff91a0d88b431a2437964ae1a6) Merged-In: Ic8eb42c369de8c94c7977b9631ff4b9084dfef01 Change-Id: Ic8eb42c369de8c94c7977b9631ff4b9084dfef01
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.