Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 56c36b3bb1e6b1baae71e4de129b3b82b38c2f87
commit56c36b3bb1e6b1baae71e4de129b3b82b38c2f87[log] [tgz]
authorAlex Buynytskyy <alexbuy@google.com>Thu Jan 19 17:42:10 2023 +0000
committerAlex Buynytskyy <alexbuy@google.com>Thu Jan 19 11:21:21 2023 -0800
treea8846040d1d22543f25c75b04a57abff9ab20ac5
parent5f326eb40ae430574fad363a6023664e46d52bc9 [diff]
Add local mode to the script.

Local mainline SDK artifacts can be built via
TARGET_BUILD_VARIANT=userdebug UNBUNDLED_BUILD_SDKS_FROM_SOURCE=true vendor/google/build/mainline_modules_sdks.sh

Bug: 260755259
Test: run locally
Change-Id: I0eb13441201d62db1686f2930957e33b4aa4ce37
1 file changed
tree: a8846040d1d22543f25c75b04a57abff9ab20ac5
  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.