2016-07-13 07:29:13 +02:00
|
|
|
// Copyright 2006 The Android Open Source Project
|
|
|
|
|
|
2017-04-04 23:25:43 +02:00
|
|
|
cc_library_headers {
|
|
|
|
|
name: "libhardware_headers",
|
2017-04-18 01:56:41 +02:00
|
|
|
header_libs: [
|
|
|
|
|
"libaudio_system_headers",
|
|
|
|
|
"libsystem_headers",
|
2017-06-26 06:28:51 +02:00
|
|
|
"libcutils_headers",
|
2017-04-18 01:56:41 +02:00
|
|
|
],
|
|
|
|
|
export_header_lib_headers: [
|
|
|
|
|
"libaudio_system_headers",
|
2017-06-26 06:28:51 +02:00
|
|
|
"libsystem_headers",
|
|
|
|
|
"libcutils_headers",
|
2017-04-18 01:56:41 +02:00
|
|
|
],
|
2017-04-14 04:14:57 +02:00
|
|
|
|
2017-04-04 23:25:43 +02:00
|
|
|
export_include_dirs: ["include"],
|
Mark as vendor_available
By setting vendor_available, the following may become true:
* a prebuilt library from this release may be used at runtime by
in a later releasse (by vendor code compiled against this release).
so this library shouldn't depend on runtime state that may change
in the future.
* this library may be loaded twice into a single process (potentially
an old version and a newer version). The symbols will be isolated
using linker namespaces, but this may break assumptions about 1
library in 1 process (your singletons will run twice).
Background:
This means that these modules may be built and installed twice --
once for the system partition and once for the vendor partition. The
system version will build just like today, and will be used by the
framework components on /system. The vendor version will build
against a reduced set of exports and libraries -- similar to, but
separate from, the NDK. This means that all your dependencies must
also mark vendor_available.
At runtime, /system binaries will load libraries from /system/lib*,
while /vendor binaries will load libraries from /vendor/lib*. There
are some exceptions in both directions -- bionic(libc,etc) and liblog
are always loaded from /system. And SP-HALs (OpenGL, etc) may load
/vendor code into /system processes, but the dependencies of those
libraries will load from /vendor until it reaches a library that's
always on /system. In the SP-HAL case, if both framework and vendor
libraries depend on a library of the same name, both versions will be
loaded, but they will be isolated from each other.
It's possible to compile differently -- reducing your source files,
exporting different include directories, etc. For details see:
https://android-review.googlesource.com/368372
None of this is enabled unless the device opts into the system/vendor
split with BOARD_VNDK_VERSION := current.
Bug: 36426473
Bug: 36079834
Test: Android-aosp_arm.mk is the same before/after
Test: build.ninja is the same before/after
Test: build-aosp_arm.ninja is the same before/after
Test: attempt to compile with BOARD_VNDK_VERSION := current
Change-Id: Ia4eb5378d941033b07673daf682e66051cd3c075
2017-04-07 23:15:17 +02:00
|
|
|
vendor_available: true,
|
2017-04-04 23:25:43 +02:00
|
|
|
}
|
|
|
|
|
|
2016-07-13 07:29:13 +02:00
|
|
|
cc_library_shared {
|
|
|
|
|
name: "libhardware",
|
|
|
|
|
|
|
|
|
|
srcs: ["hardware.c"],
|
|
|
|
|
shared_libs: [
|
|
|
|
|
"libcutils",
|
|
|
|
|
"liblog",
|
|
|
|
|
"libdl",
|
|
|
|
|
],
|
|
|
|
|
cflags: ["-DQEMU_HARDWARE"],
|
2017-04-14 04:14:57 +02:00
|
|
|
|
|
|
|
|
header_libs: ["libhardware_headers"],
|
|
|
|
|
export_header_lib_headers: ["libhardware_headers"],
|
|
|
|
|
|
Mark as vendor_available
By setting vendor_available, the following may become true:
* a prebuilt library from this release may be used at runtime by
in a later releasse (by vendor code compiled against this release).
so this library shouldn't depend on runtime state that may change
in the future.
* this library may be loaded twice into a single process (potentially
an old version and a newer version). The symbols will be isolated
using linker namespaces, but this may break assumptions about 1
library in 1 process (your singletons will run twice).
Background:
This means that these modules may be built and installed twice --
once for the system partition and once for the vendor partition. The
system version will build just like today, and will be used by the
framework components on /system. The vendor version will build
against a reduced set of exports and libraries -- similar to, but
separate from, the NDK. This means that all your dependencies must
also mark vendor_available.
At runtime, /system binaries will load libraries from /system/lib*,
while /vendor binaries will load libraries from /vendor/lib*. There
are some exceptions in both directions -- bionic(libc,etc) and liblog
are always loaded from /system. And SP-HALs (OpenGL, etc) may load
/vendor code into /system processes, but the dependencies of those
libraries will load from /vendor until it reaches a library that's
always on /system. In the SP-HAL case, if both framework and vendor
libraries depend on a library of the same name, both versions will be
loaded, but they will be isolated from each other.
It's possible to compile differently -- reducing your source files,
exporting different include directories, etc. For details see:
https://android-review.googlesource.com/368372
None of this is enabled unless the device opts into the system/vendor
split with BOARD_VNDK_VERSION := current.
Bug: 36426473
Bug: 36079834
Test: Android-aosp_arm.mk is the same before/after
Test: build.ninja is the same before/after
Test: build-aosp_arm.ninja is the same before/after
Test: attempt to compile with BOARD_VNDK_VERSION := current
Change-Id: Ia4eb5378d941033b07673daf682e66051cd3c075
2017-04-07 23:15:17 +02:00
|
|
|
vendor_available: true,
|
2016-07-13 07:29:13 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
subdirs = [
|
|
|
|
|
"modules/*",
|
|
|
|
|
"tests/*",
|
|
|
|
|
]
|
