Add VIC crt files to allowed deps

When building riscv64 targets, the minimum version is VIC, which
includes the crt libraries when building mainline modules for riscv64.
These dependencies do not appear when building for other architectures.

Apex-Size-Increase: None, libs do not appear outside of riscv64 targets.
Previous-Platform-Support: Not a new dep, just new SDK versions.
Ignore-AOSP-First: Merge conflict resolution with aosp/2677359.
Test-Info: Verified build and launch of riscv64 targets.
Bug: 291150284
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:e433f19cf71128bcb9db4404b1c4463700e70b32)
Merged-In: I340cc92af1c09b470e4a58259a843caf9022f6e9
Change-Id: I340cc92af1c09b470e4a58259a843caf9022f6e9
1 file changed
tree: 264fab4bbb4d48b3a5f229aeaca7262dbaa162e8
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  9. MODULES_OWNERS
  10. OWNERS
  11. PREBUILTS_MODULE_OWNERS
  12. PREUPLOAD.cfg
  13. README.md
README.md

packages/modules/common

This project includes mainline build and other utility code. Any library code intended for use by modules should go in frameworks/libs/modules-utils instead.

java code

This project uses a single source path for java code. All java code should go in the java directory with subdirectories corresponding to the java package. Android.bp files should go alongside the java source files, and should only include java source for a single java package to encourage good code hygiene.

Tests for java code should go in the javatests directory and follow the same structure.