commit | 3570b3ed86d0322a951a931487dd77e1e1a8e000 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Mon Mar 21 18:49:17 2022 -0700 |
committer | Colin Cross <ccross@android.com> | Mon Apr 04 16:04:52 2022 -0700 |
tree | 1cda55d0295e44cd243f5184ed513c1a103b1c1a | |
parent | 06f7176fc664944aac99d6b6ead22af321dc96ef [diff] |
Produce mappings of hashes to elf symbols and r8 dictionaries Run the symbols_map tool on each unstripped binary and proguard dictionary while copying it to produce a textproto that maps the hash to the symbol/dictionary file location. Combine the textprotos into a mapping file when producing the zipped build artifacts. Bug: 218888599 Test: m dist Change-Id: I78997e2f3b631ed74213903cc8e72415b2d7eee0
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.