Added new framework-pdf jar inside MediaProvider module

For V prebuilts (containing framework-pdf) to be buildable in older
platforms and have the correct API access, the framework-pdf needs to be
added as part of generating droidstub.

Bug: 346995836
Test: m and check api access
(cherry picked from commit f4d93fb6ae2eb98dbc07a2072ed897845e937ccb)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:f04a8add2ed9d5ab2d9fac8f863915b6a55aea5f)
Merged-In: I914e993143b210867aa7624c5dd5f65a826e637a
Change-Id: I914e993143b210867aa7624c5dd5f65a826e637a
1 file changed
tree: 138d38320a91006f7b4fcd810afc32092cdf95f9
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. Android.bp
  9. banchanHelp.sh
  10. buildspec.mk.default
  11. Changes.md
  12. CleanSpec.mk
  13. Deprecation.md
  14. envsetup.sh
  15. help.sh
  16. METADATA
  17. navbar.md
  18. OWNERS
  19. PREUPLOAD.cfg
  20. rbesetup.sh
  21. README.md
  22. tapasHelp.sh
  23. 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.