Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 2e20043b65d2a9216cdbd9fd875ad5d12d148f70
commit2e20043b65d2a9216cdbd9fd875ad5d12d148f70[log] [tgz]
authorJiakai Zhang <jiakaiz@google.com>Fri Nov 12 21:19:04 2021 +0000
committerJiakai Zhang <jiakaiz@google.com>Fri Nov 12 21:19:04 2021 +0000
tree63d9a1a9a6a37fc2253a620c7c05899934fb759c
parentd1e683a867bd4396b1e76d6563061149f61d6afe [diff]
Add new allowed dependency "libc++fs".

Bug: 205276874
Test: m nothing
Apex-Size-Increase: 40KB (or 0.1% of the ART APEX)
Previous-Platform-Support: yes (The library is statically linked.)
Aosp-First: yes
Test-Info: See above
Change-Id: I46d086079c0b0fa83455f898fb7328b94c761fb4
1 file changed
tree: 63d9a1a9a6a37fc2253a620c7c05899934fb759c
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. generate_ml_bundle.sh
  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.