Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / e926cab37252cdfe7ea202f1476bfd25acf47b81
commite926cab37252cdfe7ea202f1476bfd25acf47b81[log] [tgz]
authorColin Cross <ccross@android.com>Mon Jul 06 14:12:58 2020 -0700
committerColin Cross <ccross@android.com>Fri Jul 10 13:44:21 2020 -0700
treed23a4582395561cf4afd7f6c4cc1bea2c534f649
parentfaac5a2e7d9482b4002f3e26759aa015031f2e51 [diff]
Install symbols for JNI libraries

When building an app in Soong with JNI libraries copy the unstripped
libraries to the symbols directory in directory that matches the
installed path of the APK.

Bug: 159726429
Test: forrest
Change-Id: If8e423c7cdf3afd518761b5ab6bc857321acda46
2 files changed
tree: d23a4582395561cf4afd7f6c4cc1bea2c534f649
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. buildspec.mk.default
  9. Changes.md
  10. CleanSpec.mk
  11. Deprecation.md
  12. envsetup.sh
  13. help.sh
  14. navbar.md
  15. OWNERS
  16. rbesetup.sh
  17. README.md
  18. tapasHelp.sh
  19. Usage.txt
README.md

Android Make Build System

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.