| commit | 289e8d601120b8b33e223ee41699d45afeca21e6 | [log] [tgz] |
|---|---|---|
| author | Chih-Hung Hsieh <chh@google.com> | Thu May 24 15:13:19 2018 -0700 |
| committer | Chih-Hung Hsieh <chh@google.com> | Thu May 31 16:18:22 2018 -0700 |
| tree | 4c19e039fa59e0c8d4f6a97568f5aa5aa1ab8001 | |
| parent | d48f2a140836d3b993039c1d5cf8f06a3088c787 [diff] |
Call lld with --pack-dyn-relocs=none if my_pack_module_relocations is false * Factor out the logic that sets up my_pack_module_relocations from dynamic_binary.mk to pack_dyn_relocs_setup.mk. * Use stand-alone relocation_packer only if my_pack_module_relocations is true and my_use_clang_lld is false. Bug: 80093890 Bug: 73768157 Test: build and boot with USE_CLANG_LLD=true Change-Id: I7c4b5fcdce0754c57cff4acf86185cac65a26c40
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.