2016-07-13 07:29:13 +02:00
|
|
|
// Copyright 2006 The Android Open Source Project
|
|
|
|
|
2021-02-13 05:51:13 +01:00
|
|
|
package {
|
|
|
|
default_applicable_licenses: ["hardware_libhardware_license"],
|
|
|
|
}
|
|
|
|
|
|
|
|
// Added automatically by a large-scale-change that took the approach of
|
|
|
|
// 'apply every license found to every target'. While this makes sure we respect
|
|
|
|
// every license restriction, it may not be entirely correct.
|
|
|
|
//
|
|
|
|
// e.g. GPL in an MIT project might only apply to the contrib/ directory.
|
|
|
|
//
|
|
|
|
// Please consider splitting the single license below into multiple licenses,
|
|
|
|
// taking care not to lose any license_kind information, and overriding the
|
|
|
|
// default license using the 'licenses: [...]' property on targets as needed.
|
|
|
|
//
|
|
|
|
// For unused files, consider creating a 'fileGroup' with "//visibility:private"
|
|
|
|
// to attach the license to, and including a comment whether the files may be
|
|
|
|
// used in the current project.
|
|
|
|
// See: http://go/android-license-faq
|
|
|
|
license {
|
|
|
|
name: "hardware_libhardware_license",
|
|
|
|
visibility: [":__subpackages__"],
|
|
|
|
license_kinds: [
|
|
|
|
"SPDX-license-identifier-Apache-2.0",
|
|
|
|
"SPDX-license-identifier-BSD",
|
|
|
|
],
|
|
|
|
license_text: [
|
|
|
|
"NOTICE",
|
|
|
|
],
|
|
|
|
}
|
|
|
|
|
2017-04-04 23:25:43 +02:00
|
|
|
cc_library_headers {
|
|
|
|
name: "libhardware_headers",
|
2019-01-15 02:40:45 +01:00
|
|
|
|
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",
|
2023-05-19 02:33:13 +02:00
|
|
|
"libbluetooth-types-header",
|
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",
|
2023-05-19 02:33:13 +02:00
|
|
|
"libbluetooth-types-header",
|
2017-04-18 01:56:41 +02:00
|
|
|
],
|
2017-04-14 04:14:57 +02:00
|
|
|
|
2018-06-21 02:04:52 +02:00
|
|
|
recovery_available: true,
|
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
Merged-In: Ia4eb5378d941033b07673daf682e66051cd3c075
Change-Id: Ia4eb5378d941033b07673daf682e66051cd3c075
2017-04-07 23:15:17 +02:00
|
|
|
vendor_available: true,
|
2020-06-30 22:54:24 +02:00
|
|
|
// TODO(b/153609531): remove when no longer needed.
|
|
|
|
native_bridge_supported: true,
|
2019-01-15 02:40:45 +01:00
|
|
|
|
|
|
|
// There are three include directories currently:
|
|
|
|
// - include: this directory is the original location of libhardware headers. It is globally
|
|
|
|
// available (even if you do not depend on libhardware). Many locations also use
|
|
|
|
// LOCAL_C_INCLUDES or include_dirs to access these from a global namespace. These processes
|
|
|
|
// should replace this dependency with a direct dependency on libhardware(_headers)?.
|
|
|
|
// - include_all: this directory is for system and vendor include files. Gradually, the number of
|
|
|
|
// files here should be reduced to 0 by moving them to vendor as old code is phased out.
|
|
|
|
// - include_vendor: this directory is the current designated resting place for these headers.
|
|
|
|
// They are kept around to try to help insure existing codebases can function.
|
|
|
|
export_include_dirs: ["include_all"],
|
|
|
|
|
2018-06-21 02:04:52 +02:00
|
|
|
target: {
|
|
|
|
recovery: {
|
|
|
|
exclude_header_libs: [
|
|
|
|
"libaudio_system_headers",
|
2023-05-19 02:33:13 +02:00
|
|
|
"libbluetooth-types-header",
|
2018-06-21 02:04:52 +02:00
|
|
|
],
|
|
|
|
},
|
2023-02-02 00:53:41 +01:00
|
|
|
windows: {
|
|
|
|
enabled: true,
|
|
|
|
},
|
2019-01-15 02:40:45 +01:00
|
|
|
vendor: {
|
|
|
|
override_export_include_dirs: [
|
|
|
|
"include_all",
|
|
|
|
"include_vendor",
|
|
|
|
],
|
|
|
|
},
|
2018-06-21 02:04:52 +02:00
|
|
|
},
|
2021-12-23 03:05:30 +01:00
|
|
|
apex_available: [
|
|
|
|
"//apex_available:platform",
|
2023-05-19 02:33:13 +02:00
|
|
|
"com.android.btservices",
|
2023-04-29 00:47:54 +02:00
|
|
|
"com.android.media",
|
2022-02-09 19:14:29 +01:00
|
|
|
"com.android.media.swcodec",
|
2021-12-23 03:05:30 +01:00
|
|
|
],
|
2020-04-16 11:48:32 +02:00
|
|
|
min_sdk_version: "29",
|
2020-04-29 23:46:38 +02:00
|
|
|
host_supported: true,
|
2018-06-21 02:04:52 +02:00
|
|
|
|
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",
|
2017-05-10 19:15:07 +02:00
|
|
|
"libvndksupport",
|
2016-07-13 07:29:13 +02:00
|
|
|
],
|
2017-09-30 00:41:15 +02:00
|
|
|
cflags: [
|
|
|
|
"-DQEMU_HARDWARE",
|
|
|
|
"-Wall",
|
|
|
|
"-Werror",
|
|
|
|
],
|
2017-04-14 04:14:57 +02:00
|
|
|
|
|
|
|
header_libs: ["libhardware_headers"],
|
|
|
|
export_header_lib_headers: ["libhardware_headers"],
|
|
|
|
|
2022-11-14 20:13:56 +01:00
|
|
|
host_supported: true,
|
2018-06-21 02:04:52 +02:00
|
|
|
recovery_available: true,
|
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
Merged-In: Ia4eb5378d941033b07673daf682e66051cd3c075
Change-Id: Ia4eb5378d941033b07673daf682e66051cd3c075
2017-04-07 23:15:17 +02:00
|
|
|
vendor_available: true,
|
2017-07-24 08:19:45 +02:00
|
|
|
vndk: {
|
|
|
|
enabled: true,
|
|
|
|
support_system_process: true,
|
|
|
|
},
|
2018-06-21 02:04:52 +02:00
|
|
|
target: {
|
2022-11-14 20:13:56 +01:00
|
|
|
host: {
|
|
|
|
exclude_shared_libs: ["libvndksupport"],
|
|
|
|
},
|
2018-06-21 02:04:52 +02:00
|
|
|
recovery: {
|
|
|
|
exclude_shared_libs: ["libvndksupport"],
|
|
|
|
},
|
|
|
|
},
|
2020-04-16 11:48:32 +02:00
|
|
|
min_sdk_version: "29",
|
2016-07-13 07:29:13 +02:00
|
|
|
}
|