Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 9a6a2b640c8ddff7cea45a0e5ae598601641c2bd
commit9a6a2b640c8ddff7cea45a0e5ae598601641c2bd[log] [tgz]
authorSeth Moore <sethmo@google.com>Mon Nov 21 17:19:39 2022 -0800
committerSeth Moore <sethmo@google.com>Mon Nov 21 17:21:17 2022 -0800
tree62360f79e5b29f62df66d6bf2635f3a9d82612cd
parentd9fc88f5c3f823ab06becf4a0462e614f3a074eb [diff]
Add android.hardware.security.rkp to mainline deps

Apex-Size-Increase: 16KiB
Previous-Platform-Support: None
Aosp-First: yes
Test-Info: N/A - This is auto-generated code from AIDL tooling
Test: TH
Change-Id: If7ba644b73ce8d1caf485e1f76d6a31ea4d28d97
1 file changed
tree: 62360f79e5b29f62df66d6bf2635f3a9d82612cd
  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.