| commit | c54aa6db594ba63ab8b66b9795d96dbf05edf20c | [log] [tgz] |
|---|---|---|
| author | Jihoon Kang <jihoonkang@google.com> | Tue Mar 11 18:49:26 2025 +0000 |
| committer | Jihoon Kang <jihoonkang@google.com> | Tue Mar 11 18:57:51 2025 +0000 |
| tree | 717b59af6deed0f3430055beb3c914c655a2f782 | |
| parent | d8ee6f9d647953bb44ee9fa91e58b9418951e650 [diff] |
Generate symbols mapping files for jni libs Currently, the symbols files of the jni libs are copied to the symbols directory, but its elf mapping files are not generated. This change modifies this behavior so that the symbols coverage is increased. Test: CI Bug: 402471392 Change-Id: I00a62769b61fb5f72c54743873c8a6b53cd238d0
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.