Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / bc424cb3d0a4292259b507475bb5e8ff8850a3f4
commitbc424cb3d0a4292259b507475bb5e8ff8850a3f4[log] [tgz]
authorAndrew Walbran <qwandor@google.com>Thu May 11 14:05:10 2023 +0000
committerAndrew Walbran <qwandor@google.com>Thu May 11 14:07:49 2023 +0000
treedd9cf59c8446ce313f7c3dcd748ebd111d70e2d2
parent07171bd950f96f0be96126dbe0910d9815c785c4 [diff]
Split out separate rust_library rule for system_properties_bindgen.

This is necessary to work around an issue with the rust_bindgen build
rule. It doesn't actually build anything extra.

Aosp-First: yes
Apex-Size-Increase: no new library, this is just restructuring
Bug: 270142874
Previous-Platform-Support: N/A, no new dependency
Test: m system_properties_fuzzer
Test-Info: N/A, no new dependency
Change-Id: I52311e1d61da79113eabf3a5b7cd3b878542eff0
1 file changed
tree: dd9cf59c8446ce313f7c3dcd748ebd111d70e2d2
  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.