commit | 8421f6fb9dc29bd00244b39963b1761fcfcf29ee | [log] [tgz] |
---|---|---|
author | Christopher Ferris <cferris@google.com> | Fri Jul 20 11:22:03 2018 -0700 |
committer | Christopher Ferris <cferris@google.com> | Fri Jul 20 16:06:22 2018 -0700 |
tree | 8142453ec2ed4745dc8688f8d264b954d2c1a89b | |
parent | f6658018f6fbd53c92c910908964fca1c404427d [diff] |
Add a few unwinder tools to debug tools. These tools are useful for dumping elf information. Also, some of the scripts in development are being modified to use some of these tools, specifically, unwind_symbols. Test: Do a clean userdebug build and verify that the tools are built. Change-Id: Id26b8d2220dc542e8aa73d4b701916fa3d2ea804 Merged-In: Id26b8d2220dc542e8aa73d4b701916fa3d2ea804 (cherry picked from commit 6605dc01b4d86d4cdf3b2b4da76e239d96335fbc)
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.