Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 92cb3cb2b62081960cc1cbd4a799df9c71004533
commit92cb3cb2b62081960cc1cbd4a799df9c71004533[log] [tgz]
authorHarish Mahendrakar <harish.mahendrakar@ittiam.com>Fri May 27 15:10:47 2022 -0700
committerHarish Mahendrakar <harish.mahendrakar@ittiam.com>Fri May 27 15:16:34 2022 -0700
treeed2051a11d0e112fe60fea89816f7016f0d7c191
parentfc0ea40e8d94a5837ff5ce50bb0f9ed90bbf65c9 [diff]
Added libarect_headers to the allowed list

libarect was in the allowed list, now libarect_headers also is added

Apex-Size-Increase: 0
Previous-Platform-Support: 29 (the same as min_sdk_version of libarect)
Aosp-First: Yes.
Test-Info: No behavior change. libarect has been in the allow list. The
header variant of the lib is added as a dependency.

Bug: 214411172
Test: Builds
Change-Id: Id1fce9d809e9f334cc36f75868a98745504693b7
1 file changed
tree: ed2051a11d0e112fe60fea89816f7016f0d7c191
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. MODULES_OWNERS
  9. OWNERS
  10. PREBUILTS_MODULE_OWNERS
  11. PREUPLOAD.cfg
  12. 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.