tequilaOS/platform_build
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
platform_build/core/copy_headers.mk

54 lines
2 KiB
Makefile
Raw Normal View History

Add basic VNDK support in Make Add BOARD_VNDK_VERSION and LOCAL_USE_VNDK to specify the version of the VNDK that will be used globally, and whether to use the VNDK on a module basis. If the board is using the VNDK: * LOCAL_COPY_HEADERS may only be used by modules defining LOCAL_USE_VNDK * LOCAL_USE_VNDK modules will compile against the NDK headers and stub libraries, but continue to use the platform libc++. * LOCAL_USE_VNDK modules will not have the global includes like system/core/include, but it will use device-specific kernel headers. This change does not attempt to enforce any linking constraints, that will come in a later patch. Test: out/build-aosp_arm.ninja is identical before/after Change-Id: Icce65d4974f085093d500b5b2516983788fe2905
2016-11-18 23:05:39 +01:00
ifneq (,$(strip $(LOCAL_COPY_HEADERS)))
auto import from //depot/cupcake/@135843
2009-03-04 04:28:42 +01:00
###########################################################
## Copy headers to the install tree
###########################################################
Record module type statistics Creates a build_system_stats.txt build artifact that contains statistics on how many BUILD_* modules are defined in a build. Also writes out information about the Soong module types sent from the Soong build. Merged-In: Iaf0c7062f542dc6942b5349854f3d49267cac4a5 Change-Id: Iaf0c7062f542dc6942b5349854f3d49267cac4a5
2016-07-26 01:03:53 +02:00
$(call record-module-type,COPY_HEADERS)
auto import from //depot/cupcake/@135843
2009-03-04 04:28:42 +01:00
ifneq ($(strip $(LOCAL_IS_HOST_MODULE)),)
Stop removing valid copy headers My change to clean up obsolete copy headers would remove valid ones if thhe LOCAL_COPY_HEADERS_TO path wasn't cleaned. I'm seeing this most with values that just end in '/', so we end up with a '//' in the path, which isn't textually equivalent, and we remove it. Test: No longer seeing constant removals on internal products Test: Set LOCAL_COPY_HEADERS_TO := .. Test: Set LOCAL_COPY_HEADERS_TO := ../foo Test: Set LOCAL_COPY_HEADERS_TO := /foo Change-Id: Idbeeb207a2bb2a8da766473dbded877cec7c9cc1
2019-12-27 01:27:36 +01:00
$(call pretty-error,LOCAL_COPY_HEADERS may not be used with host modules)
auto import from //depot/cupcake/@135843
2009-03-04 04:28:42 +01:00
endif
Add basic VNDK support in Make Add BOARD_VNDK_VERSION and LOCAL_USE_VNDK to specify the version of the VNDK that will be used globally, and whether to use the VNDK on a module basis. If the board is using the VNDK: * LOCAL_COPY_HEADERS may only be used by modules defining LOCAL_USE_VNDK * LOCAL_USE_VNDK modules will compile against the NDK headers and stub libraries, but continue to use the platform libc++. * LOCAL_USE_VNDK modules will not have the global includes like system/core/include, but it will use device-specific kernel headers. This change does not attempt to enforce any linking constraints, that will come in a later patch. Test: out/build-aosp_arm.ninja is identical before/after Change-Id: Icce65d4974f085093d500b5b2516983788fe2905
2016-11-18 23:05:39 +01:00
# Modules linking against the SDK do not have the include path to use
# COPY_HEADERS, so prevent them from exporting any either.
ifdef LOCAL_SDK_VERSION
Stop removing valid copy headers My change to clean up obsolete copy headers would remove valid ones if thhe LOCAL_COPY_HEADERS_TO path wasn't cleaned. I'm seeing this most with values that just end in '/', so we end up with a '//' in the path, which isn't textually equivalent, and we remove it. Test: No longer seeing constant removals on internal products Test: Set LOCAL_COPY_HEADERS_TO := .. Test: Set LOCAL_COPY_HEADERS_TO := ../foo Test: Set LOCAL_COPY_HEADERS_TO := /foo Change-Id: Idbeeb207a2bb2a8da766473dbded877cec7c9cc1
2019-12-27 01:27:36 +01:00
$(call pretty-error,Modules using LOCAL_SDK_VERSION may not use LOCAL_COPY_HEADERS)
Add basic VNDK support in Make Add BOARD_VNDK_VERSION and LOCAL_USE_VNDK to specify the version of the VNDK that will be used globally, and whether to use the VNDK on a module basis. If the board is using the VNDK: * LOCAL_COPY_HEADERS may only be used by modules defining LOCAL_USE_VNDK * LOCAL_USE_VNDK modules will compile against the NDK headers and stub libraries, but continue to use the platform libc++. * LOCAL_USE_VNDK modules will not have the global includes like system/core/include, but it will use device-specific kernel headers. This change does not attempt to enforce any linking constraints, that will come in a later patch. Test: out/build-aosp_arm.ninja is identical before/after Change-Id: Icce65d4974f085093d500b5b2516983788fe2905
2016-11-18 23:05:39 +01:00
endif
Reapply "Rename LOCAL_USE_VNDK" LOCAL_USE_VNDK property refers if the module uses VNDK, and this property is being used to check if the module is installed in vendor or product. However, the term no longer makes sense with VNDK deprecation, so it should be renamed. Similar to change in aosp/2897612, rename LOCAL_USE_VNDK as LOCAL_IN_VENDOR or LOCAL_IN_PRODUCT. Bug: 316829758 Test: AOSP CF build succeeded Change-Id: I2da2e2027ccabbcfbb444abc6828addeb3b22e13
2024-02-05 02:22:04 +01:00
include $(BUILD_SYSTEM)/local_vendor_product.mk
Add basic VNDK support in Make Add BOARD_VNDK_VERSION and LOCAL_USE_VNDK to specify the version of the VNDK that will be used globally, and whether to use the VNDK on a module basis. If the board is using the VNDK: * LOCAL_COPY_HEADERS may only be used by modules defining LOCAL_USE_VNDK * LOCAL_USE_VNDK modules will compile against the NDK headers and stub libraries, but continue to use the platform libc++. * LOCAL_USE_VNDK modules will not have the global includes like system/core/include, but it will use device-specific kernel headers. This change does not attempt to enforce any linking constraints, that will come in a later patch. Test: out/build-aosp_arm.ninja is identical before/after Change-Id: Icce65d4974f085093d500b5b2516983788fe2905
2016-11-18 23:05:39 +01:00
Reapply "Rename LOCAL_USE_VNDK" LOCAL_USE_VNDK property refers if the module uses VNDK, and this property is being used to check if the module is installed in vendor or product. However, the term no longer makes sense with VNDK deprecation, so it should be renamed. Similar to change in aosp/2897612, rename LOCAL_USE_VNDK as LOCAL_IN_VENDOR or LOCAL_IN_PRODUCT. Bug: 316829758 Test: AOSP CF build succeeded Change-Id: I2da2e2027ccabbcfbb444abc6828addeb3b22e13
2024-02-05 02:22:04 +01:00
# Modules in vendor or product may use LOCAL_COPY_HEADERS.
# Platform libraries will not have the include path present.
ifeq ($(call module-in-vendor-or-product),)
$(call pretty-error,Only modules in vendor or product may use LOCAL_COPY_HEADERS)
Add basic VNDK support in Make Add BOARD_VNDK_VERSION and LOCAL_USE_VNDK to specify the version of the VNDK that will be used globally, and whether to use the VNDK on a module basis. If the board is using the VNDK: * LOCAL_COPY_HEADERS may only be used by modules defining LOCAL_USE_VNDK * LOCAL_USE_VNDK modules will compile against the NDK headers and stub libraries, but continue to use the platform libc++. * LOCAL_USE_VNDK modules will not have the global includes like system/core/include, but it will use device-specific kernel headers. This change does not attempt to enforce any linking constraints, that will come in a later patch. Test: out/build-aosp_arm.ninja is identical before/after Change-Id: Icce65d4974f085093d500b5b2516983788fe2905
2016-11-18 23:05:39 +01:00
endif
Stop removing valid copy headers My change to clean up obsolete copy headers would remove valid ones if thhe LOCAL_COPY_HEADERS_TO path wasn't cleaned. I'm seeing this most with values that just end in '/', so we end up with a '//' in the path, which isn't textually equivalent, and we remove it. Test: No longer seeing constant removals on internal products Test: Set LOCAL_COPY_HEADERS_TO := .. Test: Set LOCAL_COPY_HEADERS_TO := ../foo Test: Set LOCAL_COPY_HEADERS_TO := /foo Change-Id: Idbeeb207a2bb2a8da766473dbded877cec7c9cc1
2019-12-27 01:27:36 +01:00
# Clean up LOCAL_COPY_HEADERS_TO, since soong_ui will be comparing cleaned
# paths to figure out which headers are obsolete and should be removed.
LOCAL_COPY_HEADERS_TO := $(call clean-path,$(LOCAL_COPY_HEADERS_TO))
ifneq ($(filter /% .. ../%,$(LOCAL_COPY_HEADERS_TO)),)
$(call pretty-error,LOCAL_COPY_HEADERS_TO may not start with / or ../ : $(LOCAL_COPY_HEADERS_TO))
endif
ifeq ($(LOCAL_COPY_HEADERS_TO),.)
LOCAL_COPY_HEADERS_TO :=
endif
auto import from //depot/cupcake/@135843
2009-03-04 04:28:42 +01:00
# Create a rule to copy each header, and make the
# all_copied_headers phony target depend on each
# destination header. copy-one-header defines the
# actual rule.
#
$(foreach header,$(LOCAL_COPY_HEADERS), \
$(eval _chFrom := $(LOCAL_PATH)/$(header)) \
$(eval _chTo := \
avoid // in copy headers rule If LOCAL_COPY_HEADERS_TO is not set, then the copy headers rule target is set to out/target/product/../obj/include//header.h. If another rule depends on the header without the //, it will fail. Don't insert LOCAL_COPY_HEADERS_TO if it is blank. Change-Id: Ideac7f8e01288ab5cca98645b307945d6ae9e97c
2013-10-22 21:24:21 +02:00
$(if $(LOCAL_COPY_HEADERS_TO),\
Prohibit host modules from using LOCAL_COPY_HEADERS There are no users left, so remove all of this. Test: lunch aosp_arm-eng; m -j native Test: build/tools/kati_all_products.sh on aosp and internal master Change-Id: I32f5c8b470a43dd203d7e20c192167630e4e6888
2016-11-23 01:17:38 +01:00
$(TARGET_OUT_HEADERS)/$(LOCAL_COPY_HEADERS_TO)/$(notdir $(header)),\
$(TARGET_OUT_HEADERS)/$(notdir $(header)))) \
Warn more clearly when there are duplicate copied headers When more than one makefile tries to copy a header to the same destination, the warning is not clear, and hard to track down and assign blame: build/core/copy_headers.mk:15: warning: ignoring old commands for target `out/target/product/bullhead/obj/include/qcom/display/copybit.h' With this change, the same behavior is kept, but the warning message is more descriptive, and contains the offending Android.mk files: build/core/Makefile:54: Duplicate header copy: out/target/product/bullhead/obj/include/qcom/display/copybit.h build/core/Makefile:54: Defined in: hardware/qcom/display/msm8994/libcopybit/Android.mk hardware/qcom/display/msm8994/libcopybit/Android.mk In this case, a $(CLEAR_VARS) is missing, so the same Android.mk file is copying the same headers twice. Bug: 27302058 Change-Id: Icf8f580ae71a78741db21c1d8f3213424459e637
2016-02-23 22:40:07 +01:00
$(eval ALL_COPIED_HEADERS.$(_chTo).MAKEFILE += $(LOCAL_MODULE_MAKEFILE)) \
$(eval ALL_COPIED_HEADERS.$(_chTo).SRC += $(_chFrom)) \
$(if $(filter $(_chTo),$(ALL_COPIED_HEADERS)),, \
$(eval ALL_COPIED_HEADERS += $(_chTo))) \
auto import from //depot/cupcake/@135843
2009-03-04 04:28:42 +01:00
)
_chFrom :=
_chTo :=
Add basic VNDK support in Make Add BOARD_VNDK_VERSION and LOCAL_USE_VNDK to specify the version of the VNDK that will be used globally, and whether to use the VNDK on a module basis. If the board is using the VNDK: * LOCAL_COPY_HEADERS may only be used by modules defining LOCAL_USE_VNDK * LOCAL_USE_VNDK modules will compile against the NDK headers and stub libraries, but continue to use the platform libc++. * LOCAL_USE_VNDK modules will not have the global includes like system/core/include, but it will use device-specific kernel headers. This change does not attempt to enforce any linking constraints, that will come in a later patch. Test: out/build-aosp_arm.ninja is identical before/after Change-Id: Icce65d4974f085093d500b5b2516983788fe2905
2016-11-18 23:05:39 +01:00
endif # LOCAL_COPY_HEADERS
Reference in a new issue Copy permalink