654320666d
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}
21 lines
328 B
Python
21 lines
328 B
Python
include_rules = [
|
|
"+vpx",
|
|
"+call",
|
|
"+common_video",
|
|
"+system_wrappers",
|
|
"+rtc_tools",
|
|
"+third_party/libyuv",
|
|
]
|
|
|
|
specific_include_rules = {
|
|
"android_test_initializer\.cc": [
|
|
"+base/android",
|
|
"+sdk",
|
|
],
|
|
"(.*test\.cc|.*test\.h|.*test\.mm)": [
|
|
"+media/base",
|
|
"+media/engine",
|
|
"+sdk",
|
|
],
|
|
}
|