commit | 5529e36e88f8320d1f7fcab533ec3dd668b92c27 | [log] [tgz] |
---|---|---|
author | Mark Punzalan <markpun@google.com> | Wed May 15 06:12:49 2024 +0000 |
committer | Yurii Zubrytskyi <zyy@google.com> | Wed May 15 06:18:23 2024 +0000 |
tree | ef34551e1d77a46f4eb85cc67dc8dca2216cad61 | |
parent | b63973dfc217fc701d967a8cf83c71b34a54fa2c [diff] |
Add a nano proto version of aconfig protos Framework already has nano protos, and reusing them won't introduce extra dependencies for the apps This is setting up the resources flagging in the framework Bug: 297373084 Test: Built with related changes Change-Id: I518bd56f56c42e0adef0002e95f8948e0904fb43
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.