Add libmonkey_jni to base

The monkey package is already part of "base" build. In this topic, we
are adding jni support to monkey, which will allow us to use libinput's
uinput infrastructure for motion injection.

In this CL, we also need to add libmonkey_jni to the base build. Without
this change, monkey fails to find the jni library, because 'flashall'
does not include this .so by default.

However, this change is not needed when running 'adb sync', which
correctly recognizes that the jni library is required and places it in
the right place on the device.

Bug: 344695913
Flag: EXEMPT refactor
Ignore-AOSP-First: relies on uinput infra not available in aosp
Test: adb shell monkey 1000 --pct-touch 100
Test: m && vendor/google/tools/flashall -w --disable_verity=true
Change-Id: Id6c381895e914f0c0ab8278fad31e82734f48cf5
1 file changed
tree: a2c4629d7aeca9ba47f7910b8778c2c02d2d73e1
  1. ci/
  2. common/
  3. core/
  4. packaging/
  5. target/
  6. teams/
  7. tests/
  8. tools/
  9. .gitignore
  10. Android.bp
  11. banchanHelp.sh
  12. buildspec.mk.default
  13. Changes.md
  14. CleanSpec.mk
  15. cogsetup.sh
  16. Deprecation.md
  17. envsetup.sh
  18. help.sh
  19. navbar.md
  20. OWNERS
  21. PREUPLOAD.cfg
  22. rbesetup.sh
  23. README.md
  24. shell_utils.sh
  25. tapasHelp.sh
  26. 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.