Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 7dfb12814896e9e0a4693d634b0f2f4e9b03b2a2
commit7dfb12814896e9e0a4693d634b0f2f4e9b03b2a2[log] [tgz]
authorGurpreet Singh <gurpreetgs@google.com>Fri Jun 07 14:49:12 2024 +0000
committerGurpreet Singh <gurpreetgs@google.com>Fri Jun 07 15:57:25 2024 +0000
treeaf5504cc57f46bc86b4ffe92c16b7bf4be7ce633
parent67816a2eab3e63c576974e2e66b5171ac4603805 [diff]
Add module_proto_key field to MainlineModule in mainline_modules_sdks

module_proto_key field will contain a mapping between the Mainline
module and its corresponding entry in the SdkModule Enum key in
packages/modules/common/proto/sdk.proto file.

This mapping is added to mainline-modules-info.json file, which allows
fetching this mapping in google3. And hence can be used to pass these
proto keys values are parameter to the gen_sdk script when executed
in google3 via Gantry.

Bug: 321970705
Test: packages/modules/common/build/mainline_modules_sdks.sh --build-release=latest
Test: atest --host mainline_modules_sdks_test --no-bazel-mode
Change-Id: I83d14ba509f85e168e6751675bea409fd7fdba8c
3 files changed
tree: af5504cc57f46bc86b4ffe92c16b7bf4be7ce633
  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.