Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 2e2b3e10d4e00cc5492df5aa5abdfbe6072b179f
commit2e2b3e10d4e00cc5492df5aa5abdfbe6072b179f[log] [tgz]
authorMatthew Maurer <mmaurer@google.com>Tue Aug 17 14:16:09 2021 -0700
committerMatthew Maurer <mmaurer@google.com>Tue Aug 17 15:08:50 2021 -0700
tree2a7a9df91a009a8805f1b242e456a10dead95b26
parent03120ed259e1eaf7a464b6902e6c7f6a9c0d9170 [diff]
Allow Rust Demangler for runtime error reporting

Bug: 178565008
Test: killall -11, check demangled symbols
Apex-Size-Increase: 140k
Previous-Platform-Support: No platform dependencies
Aosp-First: AOSP-first
Test-Info: Unit tests run in TEST_MAPPING on project updates
Change-Id: I2af87feadacb005297e5a122e2d0b034326e909e
1 file changed
tree: 2a7a9df91a009a8805f1b242e456a10dead95b26
  1. build/
  2. java/
  3. proto/
  4. sdk/
  5. tools/
  6. Android.bp
  7. MODULES_OWNERS
  8. OWNERS
  9. PREBUILTS_MODULE_OWNERS
  10. PREUPLOAD.cfg
  11. 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.