Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 1fc1e0c1703fdb3833e4b66cc43b9963abc25ccc
commit1fc1e0c1703fdb3833e4b66cc43b9963abc25ccc[log] [tgz]
authorJustin Yun <justinyun@google.com>Wed Feb 28 11:54:24 2024 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Feb 28 11:54:24 2024 +0000
treebe8a4d208b0c9ec3fedcb6355514bc11af0f7bb1
parentcf8b0f7aedc9d37eff618a582511cd1238c33723 [diff]
parent2721689d6cda8caad8bbe1d4b925c9f489cb535a [diff]
Add libvendorsupport_llndk_headers to the allowed_deps.txt am: 82393a9648 am: 2721689d6c

Original change: https://android-review.googlesource.com/c/platform/packages/modules/common/+/2979290

Change-Id: I881064ec9bf135b1f4fb0f6cd8277b4c4eaf5d0f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: be8a4d208b0c9ec3fedcb6355514bc11af0f7bb1
  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.