Skip to content

lights.msm8960: add missing libhardware_headers dependency - #3

Open
deepsidhu1313 wants to merge 1 commit into
LineageOS-UL:lineage-21.0-caf-msm8960from
deepsidhu1313:fix-lights-msm8960-missing-header-dep
Open

deepsidhu1313 wants to merge 1 commit into
LineageOS-UL:lineage-21.0-caf-msm8960from
deepsidhu1313:fix-lights-msm8960-missing-header-dep

Conversation

@deepsidhu1313

Copy link
Copy Markdown

Found while building lineage-21.0 for flo/flox (Nexus 7 2013) via LineageOS-UL.

lights.c includes hardware/lights.h, which lives under hardware/libhardware/include_vendor (this is a LOCAL_VENDOR_MODULE) and is exported by the libhardware_headers Soong header-only module (already vendor_available). This Android.mk never declared the dependency, so the include path wasn't reaching the vendor compile. Sibling msm8960 legacy HAL modules (e.g. display/libmemtrack/Android.mk) already use this exact LOCAL_HEADER_LIBRARIES pattern -- applied it here too.

lights.c includes hardware/lights.h, which lives under
hardware/libhardware/include_vendor (this is a LOCAL_VENDOR_MODULE)
and is exported by the libhardware_headers Soong header-only module
(already vendor_available). This Android.mk never declared the
dependency, so the include path wasn't reaching the vendor compile.
Sibling qcom-caf/msm8960 legacy HAL modules (e.g.
display/libmemtrack/Android.mk) already use this exact
LOCAL_HEADER_LIBRARIES pattern -- applied it here too.

Change-Id: If3415b3686173511433fd70ca3d39c0855a5dde4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant