Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 0e8dbf88fb7126f6a55f4afb7dc38fbf95b9e656
commit0e8dbf88fb7126f6a55f4afb7dc38fbf95b9e656[log] [tgz]
authorAnton Hansson <hansson@google.com>Wed Apr 06 11:47:12 2022 +0100
committerAnton Hansson <hansson@google.com>Wed Apr 06 11:58:01 2022 +0100
treeec4612b68f73ee8228018287596fe63e817c3a31
parent27af85827a3e42537dcac9a4854196c6b371584c [diff]
Convert finalize_sdk.py to use pathlib

The legacy os path stuff is a bit cumbersome to work with.

Test: together with the rest of the CLs in this set
Change-Id: I94f7c6f04e9f3e1644b1cc6585c2c8752f6b33ef
1 file changed
tree: ec4612b68f73ee8228018287596fe63e817c3a31
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. generate_ml_bundle.sh
  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.