summaryrefslogtreecommitdiff
path: root/Android.bp
AgeCommit message (Collapse)Author
2021-02-12[LSC] Add LOCAL_LICENSE_KINDS to hardware/libhardwareBob Badour
Added SPDX-license-identifier-Apache-2.0 to: modules/audio/Android.bp modules/audio_remote_submix/Android.bp modules/audio_remote_submix/tests/Android.bp modules/camera/3_0/Android.bp modules/consumerir/Android.bp modules/fingerprint/Android.bp modules/gralloc/Android.mk modules/hwcomposer/Android.bp modules/input/evdev/Android.bp modules/local_time/Android.bp modules/nfc-nci/Android.bp modules/nfc/Android.bp modules/power/Android.bp modules/radio/Android.bp modules/sensors/Android.bp modules/sensors/Android.mk modules/sensors/dynamic_sensor/Android.bp modules/sensors/dynamic_sensor/HidUtils/Android.bp modules/soundtrigger/Android.bp modules/thermal/Android.bp modules/tv_input/Android.bp modules/usbaudio/Android.bp modules/usbcamera/Android.bp modules/vibrator/Android.bp modules/vr/Android.bp tests/camera3/Android.bp tests/fingerprint/Android.bp tests/hardware/Android.bp tests/hwc/Android.bp tests/input/evdev/Android.bp tests/nusensors/Android.bp Added SPDX-license-identifier-Apache-2.0 SPDX-license-identifier-BSD to: Android.bp modules/camera/3_4/Android.mk Bug: 68860345 Bug: 151177513 Bug: 151953481 Test: m all Exempt-From-Owner-Approval: janitorial work Change-Id: I28924363e6c478f5d0b465b63534c4efd041c770
2020-06-30Make libhardware_headers available for native_bridgeVictor Khimenko
Bug: http://b/153609531 Test: m libRSDriver.native_bridge Change-Id: I05220635027635ff12a7d5201b5c716ca4fda5ea
2020-04-29Add host_supported to libhardware_headers.A. Cody Schuffelen
This will allow building PureSoftKeymaster on the host. Bug: 155328339 Test: Compiles Change-Id: If4474fc3da715a49f2c8649a61968cdda9b1086f
2020-04-16Set min_sdk_version to be part of mainline modulesJooyung Han
Modules contributing mainline modules (APK/APEX) should set min_sdk_version as well as apex_available. For now setting min_sdk_version doesn't change build outputs. But build-time checks will be added soon. Bug: 152655956 Test: m Change-Id: Iab1437027fcbe4b7876207ec7605a765ba667b52
2018-08-10Allow libhardware to be used in recoveryJerry Zhang
The default boot ctrl implementation depends on libhardware. Bug: 78793464 Test: Compiles, can load bootctrl in recovery Change-Id: I9c8aa8b00b9b81f11736de13c85973e113056e69
2017-12-27Convert to Android.bpDan Willemsen
See build/soong/README.md for more information Test: mmma hardware/libhardware Change-Id: Ibb7e2af9d55f581e951d8996cea5e52cd0766b04
2017-10-04Use -Werror in hardware/libhardwareChih-Hung Hsieh
* Remove unused local variables and function. * Fix unused return value warning. Bug: 66996870 Test: build with WITH_TIDY=1 Change-Id: I269eca76cda2222c7a0176e85e92df0bb0924a0e
2017-08-23Mark the module as VNDK or VNDK-SP in Android.bpJustin Yun
As a VNDK/VNDK-SP module, Android.bp must have 'vndk' tag as well as 'vendor_available: true'. For a VNDK module, the 'vndk' tag has 'enabled: true'. It will be installed system/lib(64)/vndk as a vendor variant. For a VNDK-SP module, the 'vndk' tag has 'support_system_process: true' as well as 'enabled: true'. It will be installed system/lib(64)/vndk-sp as a vendor variant. Bug: 63866913 Test: build and boot with BOARD_VNDK_VERSION=current Merged-In: I383af9ccc5457afe437c0cd910c11b636e4b6dd5 Change-Id: I383af9ccc5457afe437c0cd910c11b636e4b6dd5 (cherry picked from commit 8d9fa07fe1d5d160e6514e7ecf55157f69b091d8)
2017-07-21Merge "Fix build by adding bt_types to bluetooth.h (2/2)"johnshamoon
am: 7de0e9ceae Change-Id: Ic02b634d1e77f2ae73b68b625e4cc9fb2cff8706
2017-07-21Fix build by adding bt_types to bluetooth.h (2/2)johnshamoon
Allow bt_types to be included as a shared or static library. Test: Compiles Change-Id: Idabc1da73f1d735ea874942a08ebfcd655a7833b
2017-06-27Merge "libhardware_headers export headers from libcutils"Jiyong Park
am: 4ba2ac5844 Change-Id: I367e5101f46405ac4e105f6c2c7f6a3e1d55c4df
2017-06-26libhardware_headers export headers from libcutilsJiyong Park
Some headers of libhardware are using headers from libcutils. Bug: 33241851 Test: BOARD_VNDK_VERSION=current m -j successful with aosp_arm target Change-Id: I649056285ced1cd5da4aba6a19b25e22c43c8621
2017-05-15Load legacy HAL modules from the sphal namespaceJiyong Park
'vndk' namespace should not have /vendor/lib/* in its search paths. However, /vendor/lib/* has been included due to libhardware; it should be able to load HAL libs in /vendor/lib and /vendor/lib/hw. Since the HAL libs are not vndk but part of SP-HAL, they are loaded explicitly from the 'sphal' namespace. Bug: 37731053 Bug: 37323945 Test: sailfish builds and boots successfuly Test: BOARD_VNDK_VERSION=current m libhardware.vendor successful Merged-In: I1e1619de7deaa0e6610180e585bd7775887bc562 Change-Id: I1e1619de7deaa0e6610180e585bd7775887bc562 (cherry picked from commit 4d67d2e13a8591a02c63e6f89c3dbdbf94b0c629)
2017-04-19libhardware: add libaudio_system_headersSteven Moreland
hardware/audio.h uses libaudio_system_headers Test: works with BOARD_VNDK_VERSION := current Bug: 33241851 (cherry picked from commit d24879050a28098a8a20a64d9f25e2574df180d2) Merged-In: I6042c9903b2bc580ec519b713f0f19d94e1daa2d Change-Id: I6042c9903b2bc580ec519b713f0f19d94e1daa2d
2017-04-19libhardware: export system headersSteven Moreland
libhardware uses system headers in its headers. Test: links Test: libraries using libhardware which don't have access to system headers link when BOARD_VNDK_VERSION := current. Bug: 33241851 (cherry picked from commit d39335254a55089a37ac63c2764dfe7efd292ec4) Merged-In: I33cbd8a4d6188eed69cb8b55acb3b78b0628d82a Change-Id: I33cbd8a4d6188eed69cb8b55acb3b78b0628d82a
2017-04-17libhardware: add libaudio_system_headersSteven Moreland
hardware/audio.h uses libaudio_system_headers Test: works with BOARD_VNDK_VERSION := current Bug: 33241851 Change-Id: I6042c9903b2bc580ec519b713f0f19d94e1daa2d
2017-04-13libhardware: export system headersSteven Moreland
libhardware uses system headers in its headers. Test: links Test: libraries using libhardware which don't have access to system headers link when BOARD_VNDK_VERSION := current. Bug: 33241851 Change-Id: I33cbd8a4d6188eed69cb8b55acb3b78b0628d82a
2017-04-13Merge changes Ia4eb5378,I745031b8 into oc-devTreeHugger Robot
* changes: Mark as vendor_available Export headers as libhardware_headers
2017-04-12Mark as vendor_availableDan Willemsen
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-12Export headers as libhardware_headersVijay Venkatraman
Bug: 33241851 Test: Build sailfish Merged-In: I745031b8a8099a84610bbc2224ef2b6b6ad2e70d Change-Id: I745031b8a8099a84610bbc2224ef2b6b6ad2e70d
2017-04-12Include what you useDan Willemsen
This doesn't need utils/Log.h, just log/log.h and some stdlib headers. Bug: 33241851 Test: m -j libhardware Merged-In: Id73059f5636af42b0d1680b89f6ca27f466d9ea8 Change-Id: Id73059f5636af42b0d1680b89f6ca27f466d9ea8
2017-04-10Mark as vendor_availableDan Willemsen
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-10Include what you useDan Willemsen
This doesn't need utils/Log.h, just log/log.h and some stdlib headers. Bug: 33241851 Test: m -j libhardware Change-Id: Id73059f5636af42b0d1680b89f6ca27f466d9ea8
2017-04-04Export headers as libhardware_headersVijay Venkatraman
Bug: 33241851 Test: Build sailfish Change-Id: I745031b8a8099a84610bbc2224ef2b6b6ad2e70d
2016-07-12Begin converting Android.mk to Android.bpDan Willemsen
These modules have their dependencies satisfied. Change-Id: I67986efd7478e477770bedac72ab35a407e3d06a
generated by cgit v1.2.3 (git 2.25.1) at 2025-10-03 08:58:06 +0000