Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 3ded65bbc46a1cf88b671bd29173e9de9c2c93ff
commit3ded65bbc46a1cf88b671bd29173e9de9c2c93ff[log] [tgz]
authorWonsik Kim <wonsik@google.com>Wed Oct 25 15:45:25 2023 -0700
committerWonsik Kim <wonsik@google.com>Tue Oct 31 14:24:54 2023 -0700
treeacde66e619d20fd3a911fdba1128ece7020bb368
parent02acddae26e026b256b4cfb96e1ffe9722df746d [diff]
Add libcodec2_aidl to allowed_deps

Apex-Size-Increase: 1159528
Previous-Platform-Support: yes
Aosp-First: yes
Test-Info: VTS & fuzzer for libcodec2_aidl itself, and CTS will run
           with the lib as integration tests

Test: m
Change-Id: I5835fd6669f3dc30c33af7623d738f0ebb93b359
1 file changed
tree: acde66e619d20fd3a911fdba1128ece7020bb368
  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.