| commit | 6e6a95b6063a920ca369f9fb4f6963aeeb8d4390 | [log] [tgz] |
|---|---|---|
| author | Carlos Eduardo Seo <carlos.seo@linaro.org> | Tue Feb 28 02:55:22 2023 +0000 |
| committer | Carlos Eduardo Seo <carlos.seo@linaro.org> | Thu Jun 29 12:50:10 2023 +0000 |
| tree | e02220174205adf9f94d78328008ec7c3b2439a6 | |
| parent | 3cda7834aa0add6921970dd0141f52ca7c10228d [diff] |
core: Add script to check for possible shared library duplication
Running dupcheck.sh after a build on an image performs two checks:
* Check for duplicate shared libraries by MD5.
* Check for possible duplicate shared libraries by comparing .note
and .text ELF sections.
This helps looking for unnecessary file duplication in the final images.
Test: after running the script, reports will be generated in the 'out'
directory.
Change-Id: I91c044a52002557fdc8dc65bfc9fd5f313ca00f3
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.