| commit | b195e7ab0411da4b6d5e17da31bb20516ae7b762 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Mon Jan 06 09:55:11 2020 -0800 |
| committer | Dan Willemsen <dwillemsen@google.com> | Mon Jan 06 10:25:56 2020 -0800 |
| tree | e877a60a6ab5233d842dc9b19fa6375dea65a7dd | |
| parent | 99202ec0a65060514666916590c4294190a9d0db [diff] |
Use symlinks in the build graph for jni libs Now that ninja uses lstat and can support installing arbitrary symlinks, switch jni lib symlinks from LOCAL_POST_INSTALL_CMDS to real rules. Bug: 128577186 Test: List of files under PRODUCT_OUT is the same before/after this change Test: out/target/product/generic/.installable_files now includes the symlinks Test: m installclean; m NfcNci -> symlinks installed with correct dest Test: m NfcNci; m NfcNci -> ninja: no work to do Change-Id: I078dca53ab3d93f74c36fa66d5577e6e3e0640d6
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.