Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 8bcf9b4f35c919b4cd076ef4ea7a9b80bef88124
commit8bcf9b4f35c919b4cd076ef4ea7a9b80bef88124[log] [tgz]
authorYu Liu <yudiliu@google.com>Wed Mar 01 16:42:24 2023 -0800
committerYu Liu <yudiliu@google.com>Fri Mar 03 00:11:25 2023 +0000
treee4708cc8bb43e92526ea43aa745977636531404f
parentf624556408d204afb3b12aa43a1588f33a18888d [diff]
Add extra_build_params to build_unbundled_mainline_module.sh.

This is in order to override the BUILD_BROKEN_DISABLE_BAZEL flag.

Bug: 268337606
Test: run dcla_apex_comparison_test
Merged-In: Iae29c0c7119ec2cfc641e346280bd60f861b8ae1
Change-Id: I85f5ef21f75844dc206595e34fd72ae831e62105
1 file changed
tree: e4708cc8bb43e92526ea43aa745977636531404f
  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.