platform_system_core/libutils/Android.bp

203 lines
4.1 KiB
Plaintext
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.
cc_library_headers {
name: "libutils_headers",
libutils: 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: m -j libutils Test: attempt to compile with BOARD_VNDK_VERSION := current Merged-In: I6c1279a74ef071851401e38bbdd377f13827694c Change-Id: I6c1279a74ef071851401e38bbdd377f13827694c
2017-04-12 03:43:16 +08:00
vendor_available: true,
recovery_available: true,
host_supported: true,
header_libs: [
"liblog_headers",
"libsystem_headers",
"libcutils_headers",
],
export_header_lib_headers: [
"liblog_headers",
"libsystem_headers",
"libcutils_headers",
],
export_include_dirs: ["include"],
target: {
android: {
header_libs: ["libbacktrace_headers"],
export_header_lib_headers: ["libbacktrace_headers"],
},
linux_bionic: {
enabled: true,
},
windows: {
enabled: true,
},
},
}
cc_defaults {
name: "libutils_defaults",
libutils: 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: m -j libutils Test: attempt to compile with BOARD_VNDK_VERSION := current Merged-In: I6c1279a74ef071851401e38bbdd377f13827694c Change-Id: I6c1279a74ef071851401e38bbdd377f13827694c
2017-04-12 03:43:16 +08:00
vendor_available: true,
vndk: {
enabled: true,
support_system_process: true,
},
host_supported: true,
cflags: [
"-Wall",
"-Werror",
],
include_dirs: ["external/safe-iop/include"],
header_libs: [
"libutils_headers",
],
export_header_lib_headers: [
"libutils_headers",
],
shared_libs: [
"liblog",
],
arch: {
mips: {
cflags: ["-DALIGN_DOUBLE"],
},
},
target: {
android: {
cflags: ["-fvisibility=protected"],
shared_libs: [
"libcutils",
"libdl",
"libvndksupport",
],
sanitize: {
misc_undefined: ["integer"],
},
},
host: {
cflags: ["-DLIBUTILS_NATIVE=1"],
shared: {
enabled: false,
},
},
linux_bionic: {
enabled: true,
},
darwin: {
cflags: ["-Wno-unused-parameter"],
},
windows: {
cflags: [
// Under MinGW, ctype.h doesn't need multi-byte support
"-DMB_CUR_MAX=1",
"-Wno-unused-private-field",
],
enabled: true,
},
},
}
cc_library {
name: "libutils",
defaults: ["libutils_defaults"],
srcs: [
"FileMap.cpp",
"JenkinsHash.cpp",
"NativeHandle.cpp",
"Printer.cpp",
"PropertyMap.cpp",
"RefBase.cpp",
"SharedBuffer.cpp",
"StopWatch.cpp",
"String8.cpp",
"String16.cpp",
"StrongPointer.cpp",
"SystemClock.cpp",
"Threads.cpp",
"Timers.cpp",
"Tokenizer.cpp",
"Unicode.cpp",
"VectorImpl.cpp",
"misc.cpp",
],
target: {
android: {
srcs: [
"Trace.cpp",
],
},
linux: {
srcs: [
"Looper.cpp",
],
},
},
}
cc_library {
name: "libutilscallstack",
defaults: ["libutils_defaults"],
srcs: [
"CallStack.cpp",
],
arch: {
mips: {
cflags: ["-DALIGN_DOUBLE"],
},
},
target: {
android: {
shared_libs: [
"libutils",
"libbacktrace",
],
},
linux: {
srcs: [
"ProcessCallStack.cpp",
],
},
},
}
// Include subdirectory makefiles
// ============================================================
cc_test {
name: "SharedBufferTest",
host_supported: true,
static_libs: ["libutils"],
shared_libs: ["liblog"],
srcs: ["SharedBufferTest.cpp"],
cflags: [
"-Wall",
"-Werror",
],
}