Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / a4d77f5accfb4cd3854b5772ecb39921f09c665c
commita4d77f5accfb4cd3854b5772ecb39921f09c665c[log] [tgz]
authorOrion Hodson <oth@google.com>Thu May 20 21:49:55 2021 +0100
committerOrion Hodson <oth@google.com>Fri May 21 16:06:10 2021 +0100
treef81ddd029e918b1eeaf52dbf1030ccd85aa3aef2
parent3cb8db65e5cb6119dff35d36d78c27b8b3993e48 [diff]
Add static variant of libnativehelper_compat_libc++

This allows the libcore native code in the ART Module to link against
the static variant libnativehelper_compat_libc++.

Ignore-AOSP-First: other dependencies need to land in aosp first this

Bug: 188067586
Test: m
Change-Id: I4b039b38d8560827b2acc80ea0157ce21da09150
(cherry picked from commit 3c01a8beff853f11754f4065a806aafcf6fe825b)
1 file changed
tree: f81ddd029e918b1eeaf52dbf1030ccd85aa3aef2
  1. build/
  2. java/
  3. proto/
  4. sdk/
  5. tools/
  6. Android.bp
  7. MODULES_OWNERS
  8. OWNERS
  9. PREUPLOAD.cfg
  10. 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.