Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 22a794f4991b9200e0b7d5d0e501dbfc88e75398
commit22a794f4991b9200e0b7d5d0e501dbfc88e75398[log] [tgz]
authorAnton Hansson <hansson@google.com>Thu Apr 28 14:02:47 2022 +0000
committerAnton Hansson <hansson@google.com>Fri Apr 29 11:11:54 2022 +0000
tree4f263855073dd8c9aac4636e1100455733eed62c
parent018e0d0f5403ec76f2f2a1035b099014ec442f10 [diff]
Address review comments on finalize_sdk.py

- Keep the Android.bp -- but rename to Android.bp.auto
- Use 'or' instead of 'if not'

Bug: 222050148
Test: Run finalize_sdk.py
Merged-In: I919c3d37916d3854cd0c8d59fddb8a1420f429b9
Change-Id: I919c3d37916d3854cd0c8d59fddb8a1420f429b9
1 file changed
tree: 4f263855073dd8c9aac4636e1100455733eed62c
  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.