Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / c40a062a66447c61c964c46dec4877d9a8a8e77d
commitc40a062a66447c61c964c46dec4877d9a8a8e77d[log] [tgz]
authorJohn Reck <jreck@google.com>Mon Oct 31 15:54:12 2022 -0400
committerJohn Reck <jreck@google.com>Thu Dec 01 17:38:45 2022 +0000
tree2e86f3203d18e6751ad6613c5ad010b0088782ca
parent71883fca0256d22f7b624de28f3e124d74a825ed [diff]
libui/libgui dependency update

libgui isn't supposed to be used by apex modules in the
first place, see b/214400477

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

Test: make
Change-Id: I9247744b3f65c1a3fccde5e6ca8c9bc6f7a702fb
Merged-In: I9247744b3f65c1a3fccde5e6ca8c9bc6f7a702fb
1 file changed
tree: 2e86f3203d18e6751ad6613c5ad010b0088782ca
  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.