
Since the webrtc/build/supplement.gypi file is loaded before Chromium's build/common.gypi it is the right place to override GYP variables. This makes it possible to use the approach in https://webrtc-codereview.appspot.com/48869004, which I applied to supplement.gypi in this CL, instead of the hacky approach in https://webrtc-codereview.appspot.com/48909004 (removed in this CL). R=tkchin@webrtc.org Review URL: https://webrtc-codereview.appspot.com/50729004 Cr-Commit-Position: refs/heads/master@{#9017}
53 lines
1.5 KiB
Python
53 lines
1.5 KiB
Python
{
|
|
'variables': {
|
|
'variables': {
|
|
'webrtc_root%': '<(DEPTH)/webrtc',
|
|
},
|
|
'webrtc_root%': '<(webrtc_root)',
|
|
'build_with_chromium': 0,
|
|
'conditions': [
|
|
['OS=="ios"', {
|
|
# Default to using BoringSSL on iOS.
|
|
'use_openssl%': 1,
|
|
|
|
# Set target_subarch for if not already set. This is needed because the
|
|
# Chromium iOS toolchain relies on target_subarch being set.
|
|
'conditions': [
|
|
['target_arch=="arm" or target_arch=="ia32"', {
|
|
'target_subarch%': 'arm32',
|
|
}],
|
|
['target_arch=="arm64" or target_arch=="x64"', {
|
|
'target_subarch%': 'arm64',
|
|
}],
|
|
],
|
|
}],
|
|
],
|
|
},
|
|
'target_defaults': {
|
|
'target_conditions': [
|
|
['_target_name=="sanitizer_options"', {
|
|
'conditions': [
|
|
['lsan==1', {
|
|
# Replace Chromium's LSan suppressions with our own for WebRTC.
|
|
'sources/': [
|
|
['exclude', 'lsan_suppressions.cc'],
|
|
],
|
|
'sources': [
|
|
'<(webrtc_root)/build/sanitizers/lsan_suppressions_webrtc.cc',
|
|
],
|
|
}],
|
|
['tsan==1', {
|
|
# Replace Chromium's TSan v2 suppressions with our own for WebRTC.
|
|
'sources/': [
|
|
['exclude', 'tsan_suppressions.cc'],
|
|
],
|
|
'sources': [
|
|
'<(webrtc_root)/build/sanitizers/tsan_suppressions_webrtc.cc',
|
|
],
|
|
}],
|
|
],
|
|
}],
|
|
],
|
|
},
|
|
}
|