platform_system_core/libcutils/Android.bp

181 lines
4.6 KiB
Text
Raw Normal View History

//
// Copyright (C) 2008 The Android Open Source Project
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
//
// some files must not be compiled when building against Mingw
// they correspond to features not used by our host development tools
// which are also hard or even impossible to port to native Win32
libcutils_nonwindows_sources = [
"android_get_control_file.cpp",
"fs.cpp",
"multiuser.cpp",
"socket_inaddr_any_server_unix.cpp",
"socket_local_client_unix.cpp",
"socket_local_server_unix.cpp",
"socket_network_client_unix.cpp",
"sockets_unix.cpp",
"str_parms.cpp",
]
cc_library_headers {
name: "libcutils_headers",
libcutils: 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: m -j libcutils Test: attempt to compile with BOARD_VNDK_VERSION := current Test: (sanity) boot internal marlin (cherry picked from commit 9610c548a8e9018ecdfbe3d7204e8fd70d2554fc) Merged-In: I76f9b28ef08a26d84d1365881e00696cc1dcfe5d Change-Id: I76f9b28ef08a26d84d1365881e00696cc1dcfe5d
2017-04-13 23:29:58 +02:00
vendor_available: true,
host_supported: true,
export_include_dirs: ["include"],
target: {
libcutils: 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: m -j libcutils Test: attempt to compile with BOARD_VNDK_VERSION := current Test: (sanity) boot internal marlin (cherry picked from commit 9610c548a8e9018ecdfbe3d7204e8fd70d2554fc) Merged-In: I76f9b28ef08a26d84d1365881e00696cc1dcfe5d Change-Id: I76f9b28ef08a26d84d1365881e00696cc1dcfe5d
2017-04-13 23:29:58 +02:00
vendor: {
export_include_dirs: ["include_vndk"],
},
linux_bionic: {
enabled: true,
},
windows: {
enabled: true,
},
},
}
cc_library {
name: "libcutils",
libcutils: 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: m -j libcutils Test: attempt to compile with BOARD_VNDK_VERSION := current Test: (sanity) boot internal marlin (cherry picked from commit 9610c548a8e9018ecdfbe3d7204e8fd70d2554fc) Merged-In: I76f9b28ef08a26d84d1365881e00696cc1dcfe5d Change-Id: I76f9b28ef08a26d84d1365881e00696cc1dcfe5d
2017-04-13 23:29:58 +02:00
vendor_available: true,
vndk: {
enabled: true,
support_system_process: true,
},
host_supported: true,
srcs: [
"config_utils.cpp",
"fs_config.cpp",
"canned_fs_config.cpp",
"hashmap.cpp",
"iosched_policy.cpp",
"load_file.cpp",
"native_handle.cpp",
"open_memstream.c",
"record_stream.cpp",
"sched_policy.cpp",
"sockets.cpp",
"strdup16to8.cpp",
"strdup8to16.cpp",
"strlcpy.c",
"threads.cpp",
],
target: {
linux_bionic: {
enabled: true,
},
not_windows: {
srcs: libcutils_nonwindows_sources + [
"ashmem-host.cpp",
"trace-host.cpp",
],
},
windows: {
srcs: [
"socket_inaddr_any_server_windows.cpp",
"socket_network_client_windows.cpp",
"sockets_windows.cpp",
],
enabled: true,
shared: {
enabled: false,
},
cflags: [
"-D_GNU_SOURCE",
],
},
android: {
srcs: libcutils_nonwindows_sources + [
"android_reboot.cpp",
"ashmem-dev.cpp",
"klog.cpp",
"partition_utils.cpp",
"properties.cpp",
"qtaguid.cpp",
"trace-dev.cpp",
"uevent.cpp",
],
},
android_arm: {
srcs: ["arch-arm/memset32.S"],
sanitize: {
misc_undefined: ["integer"],
},
},
android_arm64: {
srcs: ["arch-arm64/android_memset.S"],
sanitize: {
misc_undefined: ["integer"],
},
},
android_mips: {
srcs: ["arch-mips/android_memset.c"],
sanitize: {
misc_undefined: ["integer"],
},
},
android_mips64: {
srcs: ["arch-mips/android_memset.c"],
sanitize: {
misc_undefined: ["integer"],
},
},
android_x86: {
srcs: [
"arch-x86/android_memset16.S",
"arch-x86/android_memset32.S",
],
// TODO: This is to work around b/29412086.
// Remove once __mulodi4 is available and move the "sanitize" block
// to the android target.
sanitize: {
misc_undefined: [],
},
},
android_x86_64: {
srcs: [
"arch-x86_64/android_memset16.S",
"arch-x86_64/android_memset32.S",
],
sanitize: {
misc_undefined: ["integer"],
},
},
},
shared_libs: ["liblog"],
header_libs: [
"libcutils_headers",
"libutils_headers",
],
export_header_lib_headers: ["libcutils_headers"],
local_include_dirs: ["include"],
cflags: [
"-Werror",
"-Wall",
"-Wextra",
],
}
subdirs = ["tests"]