
Using fully qualified paths to include libyuv headers allows WebRTC to avoid to rely on the //third_party/libyuv:libyuv_config target to set the -I compiler flag. Today some WebRTC targets depend on //third_party/libyuv only to include //third_party/libyuv:libyuv_config but with fully qualified paths this should not be needed anymore. A follow-up CL will remove //third_party/libyuv from some targets that don't need it because they are not including libyuv headers. Bug: webrtc:8605 Change-Id: Icec707ca761aaf2ea8088e7f7a05ddde0de2619a No-Try: True Reviewed-on: https://webrtc-review.googlesource.com/28220 Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Magnus Flodman <mflodman@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21209}
27 lines
510 B
Python
27 lines
510 B
Python
include_rules = [
|
|
"+api",
|
|
"+call",
|
|
"+common_video",
|
|
"+logging/rtc_event_log",
|
|
"+modules/audio_coding",
|
|
"+modules/audio_device",
|
|
"+modules/audio_mixer",
|
|
"+modules/audio_processing",
|
|
"+modules/rtp_rtcp",
|
|
"+modules/video_capture",
|
|
"+modules/video_coding",
|
|
"+p2p",
|
|
"+pc",
|
|
"+sound",
|
|
"+system_wrappers",
|
|
"+voice_engine",
|
|
"+usrsctplib",
|
|
"+third_party/libyuv",
|
|
]
|
|
|
|
specific_include_rules = {
|
|
"win32devicemanager\.cc": [
|
|
"+third_party/logitech/files/logitechquickcam.h",
|
|
],
|
|
}
|