| commit | a45f5833c02634a70c76381bab308bd6745043f3 | [log] [tgz] |
|---|---|---|
| author | Ryan Prichard <rprichard@google.com> | Tue Mar 27 22:16:31 2018 -0700 |
| committer | Ryan Prichard <rprichard@google.com> | Thu Mar 29 01:39:07 2018 +0000 |
| tree | 2cb0db09b2a5206ef2d34c4d05661782d6699cba | |
| parent | c209fb179969a2a44dc0071d506135b7ee178212 [diff] |
Fix mini_debug_info stripping when no symbols should be kept. If there are no symbols to keep (i.e. all function symbols are also in the dynsym table), then the $@.keep_symbols file has size 0. When objcopy parses a --keep-symbols file, it has a special case for 0-sized files where it silently fails (exits with status 1, no error message). On the other hand, objcopy is happy with a file containing no symbols, as long as there is some whitespace or a comment. Avoid the special case by appending a newline to keep_symbols. Bug: b/62815515 Bug: b/77242617 Test: manual Change-Id: I348593164fe78ece5c85db3d28c7daccce3a52fb
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.