| commit | d99da8fa1703018725d6784f6aeae74ed2e50d76 | [log] [tgz] |
|---|---|---|
| author | Pierre Couillaud <pierre@broadcom.com> | Tue Jun 02 13:13:32 2020 -0700 |
| committer | J. Avila <elavila@google.com> | Thu Jun 04 00:17:58 2020 +0000 |
| tree | 80c2aeae23269f1e3a7053828edbed009f5a8808 | |
| parent | 49efd2aad098676165f8604233452a2c0082c136 [diff] |
Strip debug symbols from modules (fixup)
allow to also skip the stripping of the modules present in vendor
ramdisk when the BOARD configuration is set to skip the strip step.
there is also a shortcoming of this functionality: it currently assumes
the modules to strip are all created equal against the same arch in
particular, however this does not work for kernel modules which are
for mixed mode platforms, as example {kernel,android} == {aarch64,armv7}
because it will select the "android" mode strip which is unaware of the
kernel mode architecture.
Bug: 156395749
Bug: 155193290
Change-Id: I35ef51845224e94e3e253acdeb6bb14b990a401b
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.