Gitiles
Code Review Sign In
review.evervolv.com / android_packages_modules_common / e9e74dcbfa9993e8f6e5a7bc2115add4b195273f
commite9e74dcbfa9993e8f6e5a7bc2115add4b195273f[log] [tgz]
authorMotomu Utsumi <motomuman@google.com>Wed Feb 05 17:41:16 2025 +0900
committerMotomu Utsumi <motomuman@google.com>Wed Feb 26 15:25:28 2025 +0900
treedfb6979ea0efb541b47ce6c7e39249865d85efa1
parentbec8d27040e3f047e781452c037a18d8bb4333d8 [diff]
Add libbpf and dependencies to allow_deps

Bpfloader in tethering module will use libbpf

Apex-Size-Increase: libbpf.so(1.1M)
Previous-Platform-Support: yes
Aosp-First: true
Test-Info: Boot

Test: m
Bug: 394492034
Change-Id: I6b92e08a293e9fbbaefd56d4284b08d09cd728bb
1 file changed
tree: dfb6979ea0efb541b47ce6c7e39249865d85efa1
  1. Android.bp
  2. MODULES_OWNERS
  3. OWNERS
  4. PREBUILTS_MODULE_OWNERS
  5. PREUPLOAD.cfg
  6. README.md
  7. build/
  8. java/
  9. javatests/
  10. proguard/
  11. proto/
  12. sdk/
  13. tools/
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.