Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 5dcaf63c5ae3ccd4149a06067018359b49791d94
commit5dcaf63c5ae3ccd4149a06067018359b49791d94[log] [tgz]
authorAlex Buynytskyy <alexbuy@google.com>Thu Feb 16 18:12:45 2023 +0000
committerAlex Buynytskyy <alexbuy@google.com>Thu Feb 16 18:12:45 2023 +0000
tree37c57e01b607e3273aada54334a7bdbf77181dab
parent8c576009266a2ae812592f199be3ad315336943c [diff]
Add new sdk-> repo mapping to finalize_sdk.py

The script tries to automatically work out the right directory
for a given sdk name, but some modules don't fit the current
heuristic. Add those in manually.

Test: run finalize_sdk.py
Change-Id: I1eeedae80edfe1dc4d7a7dc27402f40189d00644
1 file changed
tree: 37c57e01b607e3273aada54334a7bdbf77181dab
  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.