commit | 4aa9769c04904677959d1bc22f3c0b0a4d06d56d | [log] [tgz] |
---|---|---|
author | Spandan Das <spandandas@google.com> | Fri Mar 21 17:48:29 2025 +0000 |
committer | Spandan Das <spandandas@google.com> | Fri Mar 21 17:48:29 2025 +0000 |
tree | 66a30874597e06822c292daa737e2b461ecf1804 | |
parent | db5f730f9d3c515dbb193fbf84b4ad1ffc6e7792 [diff] |
Export some board config vars to Soong These will become properties on the autogenerated android_device module, and will be used to create misc_info.txt Test: presubmits Bug: 398036609 Change-Id: I3ff1c1976754041b763811d4212508f1eddb5153
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.