Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / dc63d0da62a3b87d80dfd4cc6cb6538fd0c4783a
commitdc63d0da62a3b87d80dfd4cc6cb6538fd0c4783a[log] [tgz]
authorPrashanth Swaminathan <prashanthsw@google.com>Wed Jul 26 10:32:26 2023 -0700
committerPrashanth Swaminathan <prashanthsw@google.com>Thu Jul 27 00:31:40 2023 +0000
treecc3bc138e1ef7dafdc7a2cf181a7afb7a8722065
parentfdcc39e8a490c3a4366f062ebafcd13a5565db1e [diff]
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.
Aosp-First: AOSP-first
Test-Info: Verified build and launch of riscv64 targets.
Bug: 291150284
Merged-In: I340cc92af1c09b470e4a58259a843caf9022f6e9
Change-Id: If11ef302026b99378f6be308b63217d4e08bd6da
1 file changed
tree: cc3bc138e1ef7dafdc7a2cf181a7afb7a8722065
  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.