2016-07-28 01:36:36 +08:00
|
|
|
// Shared library for target
|
|
|
|
// ========================================================
|
|
|
|
cc_library {
|
|
|
|
name: "libnativeloader",
|
|
|
|
host_supported: true,
|
|
|
|
srcs: ["native_loader.cpp"],
|
|
|
|
shared_libs: [
|
|
|
|
"libnativehelper",
|
|
|
|
"liblog",
|
|
|
|
"libcutils",
|
2016-05-30 11:16:08 +08:00
|
|
|
"libnativebridge",
|
2016-12-21 13:22:00 +08:00
|
|
|
"libbase",
|
2016-07-28 01:36:36 +08:00
|
|
|
],
|
|
|
|
cflags: [
|
|
|
|
"-Werror",
|
|
|
|
"-Wall",
|
|
|
|
],
|
|
|
|
cppflags: [
|
|
|
|
"-fvisibility=hidden",
|
|
|
|
],
|
|
|
|
export_include_dirs: ["include"],
|
Don't install unnecessary VNDK libs
vndk_package is a phony module that includes ALL VNDK libs found in the
source code. As a result, VNDK libs that were actually not needed for
the device have been installed consuming storage. For example,
/system/lib/vndk/android.hardware.automotive*.so files were installed
even though walleye/taimen do not have automotive HALs.
VNDK libs are now installed by their link time dependencies (i.e. if a
vendor module uses libcutils, then /system/lib[64]/vndk-sp/libcutils.so
is automatically installed.).
By the way, there is a few number of VNDK libs that do not have any
link time dependency from vendor modules. They are always opened via
dlopen. In such cases, the vndk modules are added to `required`
or `LOCAL_REQUIRED_MODULES` of the module that dlopens them.
Bug: 67002788
Test: walleye builds and boots to the UI
Test: basic functionalities work (sound, camera, camcorder, slow-mo,
youtube, wifi, bluetooth)
Change-Id: I321256b9d20f20a9062c6d13b1745d8727eda558
2017-12-18 19:43:35 +08:00
|
|
|
required: [
|
|
|
|
"llndk.libraries.txt",
|
|
|
|
"vndksp.libraries.txt",
|
|
|
|
],
|
2016-07-28 01:36:36 +08:00
|
|
|
}
|