18082bd61f
Library to handle dynamic sensor connection. There are two way to use
this: as hal extension or standalone hal module.
In hal extension mode: add libdynamic_sensor_ext in dependency of hal,
instantiate DynamicSensorManager with appropriate parameters. Then
for all sensor requests, if the handle is owned by dynamic sensor
manager, forward the request.
In standalone mode, add sensor.dynamic_sensor_hal into device make
file. Usually, this also means multihal is necessary. Add
sensor.dynamic_sensor_hal into multihal configuration file.
A dummy sensor module is included for testing.
Test: tested with cts dynamics sensor related test and demo app.
also verified sensor basic operation with sensor logger.
Change-Id: I16612935fc21b06c173aca875401ece37c6bde01
59 lines
2.7 KiB
Makefile
59 lines
2.7 KiB
Makefile
# Copyright (C) 2007 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.
|
|
#
|
|
|
|
# If you don't need to do a full clean build but would like to touch
|
|
# a file or delete some intermediate files, add a clean step to the end
|
|
# of the list. These steps will only be run once, if they haven't been
|
|
# run before.
|
|
#
|
|
# E.g.:
|
|
# $(call add-clean-step, touch -c external/sqlite/sqlite3.h)
|
|
# $(call add-clean-step, rm -rf $(PRODUCT_OUT)/obj/STATIC_LIBRARIES/libz_intermediates)
|
|
#
|
|
# Always use "touch -c" and "rm -f" or "rm -rf" to gracefully deal with
|
|
# files that are missing or have been moved.
|
|
#
|
|
# Use $(PRODUCT_OUT) to get to the "out/target/product/blah/" directory.
|
|
# Use $(OUT_DIR) to refer to the "out" directory.
|
|
#
|
|
# If you need to re-do something that's already mentioned, just copy
|
|
# the command and add it to the bottom of the list. E.g., if a change
|
|
# that you made last week required touching a file and a change you
|
|
# made today requires touching the same file, just copy the old
|
|
# touch step and add it to the end of the list.
|
|
#
|
|
# ************************************************
|
|
# NEWER CLEAN STEPS MUST BE AT THE END OF THE LIST
|
|
# ************************************************
|
|
|
|
# For example:
|
|
#$(call add-clean-step, rm -rf $(OUT_DIR)/target/common/obj/APPS/AndroidTests_intermediates)
|
|
#$(call add-clean-step, rm -rf $(OUT_DIR)/target/common/obj/JAVA_LIBRARIES/core_intermediates)
|
|
#$(call add-clean-step, find $(OUT_DIR) -type f -name "IGTalkSession*" -print0 | xargs -0 rm -f)
|
|
#$(call add-clean-step, rm -rf $(PRODUCT_OUT)/data/*)
|
|
|
|
# ************************************************
|
|
# NEWER CLEAN STEPS MUST BE AT THE END OF THE LIST
|
|
# ************************************************
|
|
|
|
$(call add-clean-step, rm -f $(PRODUCT_OUT)/system/lib/libdynamic_sensor_ext.so)
|
|
$(call add-clean-step, rm -f $(PRODUCT_OUT)/system/lib64/libdynamic_sensor_ext.so)
|
|
$(call add-clean-step, rm -f $(PRODUCT_OUT)/system/lib/hw/sensors.dynamic_sensor_hal.so)
|
|
$(call add-clean-step, rm -f $(PRODUCT_OUT)/system/lib64/hw/sensors.dynamic_sensor_hal.so)
|
|
|
|
# ************************************************
|
|
# NEWER CLEAN STEPS MUST BE AT THE END OF THE LIST
|
|
# ************************************************
|
|
|