tequilaOS/platform_hardware_interfaces
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
platform_hardware_interfaces/CleanSpec.mk

87 lines
5.8 KiB
Makefile
Raw Normal View History

Move hidl shims to the vendor partition. We need google shims on the vendor partition because they are providing an implementation of a vendor defined interface. They were written by google just as a courtesy/to make the transition easier. They're basically a set for vendors to assemble their hal implementations from. Bug: 34135607 Test: marlin persist.hal.binderization on/off Change-Id: I3f86c77c147514fe470f08088a66de312ae32d4e
2017-01-12 22:33:16 +01:00
# Copyright 2017 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/*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/bin/hw/android.hardware*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/lib/hw/android.hardware*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/lib64/hw/android.hardware*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/etc/init/android.hardware*)
Bluetooth: move to vendor partition. Bug: 35328775 Test: works in both binderized and passthrough modes Change-Id: I18f21b53c2282e27342a58716475ae213a2837d4
2017-02-27 17:58:08 +01:00
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/bin/hw/android.hardware.bluetooth*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/lib/hw/android.hardware.bluetooth*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/lib64/hw/android.hardware.bluetooth*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/etc/init/android.hardware.bluetooth*)
Replace OUT with OUT_DIR OUT is only defined if some functions in envsetup.sh are run, which is not the case on the build servers. I'm looking at removing the environment variable in local builds to keep things consistent. In this case, OUT_DIR was actually expected, not OUT, which is equivalent to PRODUCT_OUT. Test: none Change-Id: I1e5e9f40727104716212d696927d1a32d7a74fab
2017-11-09 01:05:10 +01:00
$(call add-clean-step, rm -rf $(OUT_DIR)/soong/.intermediates/)
Actually fix build breakage with cleanspec. OUT_DIR instead of OUT Test: manual Change-Id: I2e48c6f2f39ff2318517ff55cbfa6ca912c05021
2017-05-11 00:32:32 +02:00
$(call add-clean-step, rm -rf $(OUT_DIR)/soong/.intermediates/hardware/interfaces/)
Update makefiles. Note cleanspec required because of b/38205169 (genrule doesn't delete output files before building, so when removing some, they get stale). Test: power vts test compiles Change-Id: Ie7ef0fc3d943a75fe898238cf861fb7f99f4146b Fixes: 35813011
2017-05-12 22:02:04 +02:00
$(call add-clean-step, rm -rf $(OUT_DIR)/soong/.intermediates/hardware/interfaces/)
Build automotive hals with VNDK. Bug: 37342627 Test: cd hardware/interfaces/automotive && BOARD_VNDK_VERSION=current mma -j64 -k Change-Id: I89e9af8a5fded3a31eedb9942cfba8e8d9614f53
2017-07-11 21:53:12 +02:00
$(call add-clean-step, find $(PRODUCT_OUT)/system $(PRODUCT_OUT)/vendor -type f -name "android\.hardware\.configstore*" -print0 | xargs -0 rm -f)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/bin/hw/android.hardware.automotive*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/lib/hw/android.hardware.automotive*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/lib64/hw/android.hardware.automotive*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/etc/init/android.hardware.automotive*)
HAL interface libs for testing are now built as test lib The HAL interfaces for testing were copied to /system/lib[64]/vndk directory since they are built as cc_library and thus falsely recognized as members of VNDK, which isn't true. Build them as cc_test_library so that they are filtered out. To do so, .hidl_for_test files are added for the test HALs and update-makefiles.sh were ran. Bug: 64776708 Test: no android.hardware.tests.*.so file in /system/lib[64]/vndk on 2017 pixel devices Change-Id: I5314db6cc08a43bccfc4521d4b80b614a91e7e48
2017-08-29 07:20:59 +02:00
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/lib/android.hardware.tests*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/lib/vndk/android.hardware.tests*)
android.hardware.graphics.allocator@2.0 is no longer VNDK-SP The interface lib has been in VNDK-SP because android.hardware.graphics.mapper@1.0 was using it. However, since the dependency has gone [1], there is no need keep it in VNDK-SP. The VNDK-SP set should be kept as small as possible because libs in VNDK-SP are subject to double-loading. Unmark the 'support_system_process' property to exclude the lib from VNDK-SP. Bug: 69480083 Test: walleye boots to the UI Change-Id: I8722c1ac15ddf56a627a12a0c649b4d734e5e5cd
2017-11-21 02:34:30 +01:00
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/lib/vndk-sp/android.hardware.graphics.allocator*)
Configstore HAL is down-revisioned to 1.0 Configstore was up-revisioned from 1.0 to 1.1. However no new APIs were added to 1.1. Therefore configstore in master will be down revisioned to 1.0. Bug: 71555815 Test: lshal | grep configsotre Test: "cat proc/<configstore pid>/status | grep Seccomp " return: Seccomp: 2 Change-Id: I65d2dc06fbe12d0c0ccc020bbd287e0b14320f2f
2017-07-10 06:56:10 +02:00
$(call add-clean-step, find $(PRODUCT_OUT)/system $(PRODUCT_OUT)/vendor -type f -name "android\.hardware\.configstore\@1\.1*" -print0 | xargs -0 rm -f)
configstore: configstore HAL uprev'ed to 1.1 This change provides a reference implementation of the configstore HAL v1.1. Bug: 69691076 Test: tested on walleye-userdebug Change-Id: I68ee224bcbda64f6fef91e8a0f95adb32d504aad
2017-04-28 11:29:40 +02:00
$(call add-clean-step, find $(PRODUCT_OUT)/system $(PRODUCT_OUT)/vendor -type f -name "android\.hardware\.configstore*" -print0 | xargs -0 rm -f)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/vendor/etc/seccomp_policy/configstore@1.0.policy)
[ConfigStore] Add useColorManagement method. Previously we couple wide color gamut display and color management together, which is because we only do color management when we have wide color gamut display. However, we would also want display that doesn't support wide color gamut but is calibrated and is capable of managing sRGB gamut to have color management. This means we will decouple wide color gamut display from color management, a device can indicate that it's color managed without having wide color gamut display and only manage color within sRGB gamut. BUG: 111505327 Test: BUild, flash and check Natural/Boosted mode. Change-Id: If1241ce040a6f691609d8f8d72a2d6f3141557cf
2018-07-21 01:03:46 +02:00
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/vendor/etc/seccomp_policy/configstore@1.1.policy)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/vendor/bin/hw/android.hardware.configstore@1.1-service)
CleanSpec: Remove stale configstore@1.1-service.rc Removing this file was inadvertently left out of commit 2b3f826. Bug: 113292034 Test: build+flash from tree before 2b3f826, sync past 2b3f826, apply this change, build+flash again Change-Id: Ic12e57e2426d2e105e6b846fa8ca076c6100c2ba
2018-08-29 22:46:25 +02:00
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/vendor/etc/init/android.hardware.configstore@1.1-service.rc)
Clean cas@1.0 file for Incremental build after enable cas@1.1 Clean cas@1.0 files from build for Incremental build Test: Manual bug: 124116613 Change-Id: I40a136dfbd0a8558e593897df3d3dd32114dd436
2019-02-08 20:31:16 +01:00
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/vendor/bin/hw/android.hardware.cas@1.0*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/vendor/etc/init/android.hardware.cas@1.0*)
CleanSpec: cas@1.0 manifest fragments Change-Id: Id96b46ffd9c443d6bcfdf87a16aa7758859b668c Fixes: 124121446 Test: manual
2019-02-12 00:35:12 +01:00
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/vendor/etc/vintf/manifest/android.hardware.cas@1.0*)
Remove configstore 1.2 the configstore functionality was added in Q. But The configstore will be deleted. So additional function is deleted. Bug: 124531214 Test: build & boot Test: adb shell lshal | grep configstore & check configstore 1.2 Change-Id: Idbb00b972bc082bd75bba94dbff9cee19df48b89
2019-02-22 03:52:42 +01:00
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/vendor/etc/init/android.hardware.configstore@1.2-service.rc)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/vendor/bin/hw/android.hardware.configstore@1.2-service)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/vendor/etc/seccomp_policy/configstore.policy)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/apex/com.android.media.swcodec/lib64/android.hardware.configstore@1.2.so)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/lib64/vndk-Q/android.hardware.configstore@1.2.so)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/lib64/android.hardware.configstore@1.2.so)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/lib/vndk-Q/android.hardware.configstore@1.2.so)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/system/lib/android.hardware.configstore@1.2.so)
Convert audio HAL service mk to bp and rename the service The service supports multiple versions and its name should not be version dependant. For backward compatibility, keep the target name android.hardware.audio@2.0-service (32bit only), existing PRODUCT_PACKAGES do not have to be updated. New products should depend on android.hardware.audio.service:32. Additionally migrate to Android.bp, dropping support for AUDIOSERVER_MULTILIB. Previously the HAL service architecture (32 vs 64) would be the same as the audio server. This in not wanted as all android audio HAL are 32 bits. Bug: 121208203 Test: # Compare following commands before and after patch: find $ANDROID_PRODUCT_OUT/vendor -name 'android.hardware.audio*'|xargs file adb shell reboot # check device boots to UI and # check the HAL restarts after the audioserver is killed adb shell ps |grep audio; adb shell killall audioserver; adb shell ps Change-Id: I25f41735175a6687a051ca1e5a7fee670eb8115e Merged-In: I25f41735175a6687a051ca1e5a7fee670eb8115e Signed-off-by: Kevin Rocard <krocard@google.com>
2019-06-19 01:38:16 +02:00
$(call add-clean-step, rm -f $(PRODUCT_OUT)/etc/init/android.hardware.audio@2.0-service.rc $(PRODUCT_OUT)/vendor/bin/hw/android.hardware.audio@2.0-service)
Update cas@1.1 hal to cas@1.2. Test: Manual bug: 141783130 Change-Id: I0c3e9041a2057ce721a608cf3a9f0a9bb15a2305 Merged-In: I0c3e9041a2057ce721a608cf3a9f0a9bb15a2305
2019-10-12 02:30:15 +02:00
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/vendor/bin/hw/android.hardware.cas@1.1*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/vendor/etc/init/android.hardware.cas@1.1*)
$(call add-clean-step, rm -rf $(PRODUCT_OUT)/vendor/etc/vintf/manifest/android.hardware.cas@1.1*)
Reference in a new issue Copy permalink