Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 681fcc852a730ac767eb6c39f0e1e01effca942c
commit681fcc852a730ac767eb6c39f0e1e01effca942c[log] [tgz]
authorLiz Kammer <eakammer@google.com>Fri Jan 28 15:30:04 2022 -0500
committerLiz Kammer <eakammer@google.com>Wed Feb 02 14:07:45 2022 +0000
tree8c760f8eb8cfcad5af1ba9a5902e309708e9ee06
parent672da8a84cd48275bd2c8c224d699f36797621f9 [diff]
Change cur_sdkinfo_src to a genrule

Bazel is more strict about only accepting srcs, not directories
as inputs, so the ability to specify a directory will become
limited in Soong.

Test: m cur_sdkinfo_src && diff before/after
Change-Id: I95e6300fb2ef793ee0231589be7fc35eb5a8d882
1 file changed
tree: 8c760f8eb8cfcad5af1ba9a5902e309708e9ee06
  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.