Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 53098a6ccd9de9f2baae8c3360f2be61b4fdf54a
commit53098a6ccd9de9f2baae8c3360f2be61b4fdf54a[log] [tgz]
authorJohn Reck <jreck@google.com>Thu Dec 08 14:04:12 2022 -0500
committerJohn Reck <jreck@google.com>Thu Jan 05 12:25:50 2023 -0500
tree4b5019771e7290927241f884920fe2ba762abc91
parentf59bfdc690c2c239fadbdeb8a77a233bd2c0c45f [diff]
Add libui dependencies

Previous-Platform-Support: n/a
Test-Info: n/a
Apex-Size-Increase: n/a
Aosp-First: n/a

Test: make
Change-Id: Ia5d260982be6a4f63b9a97a8672c3b82ef42c23e
1 file changed
tree: 4b5019771e7290927241f884920fe2ba762abc91
  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.