summaryrefslogtreecommitdiffstats
path: root/remoting/remoting.gyp
diff options
context:
space:
mode:
authorjohannkoenig <johannkoenig@google.com>2016-03-02 05:54:31 -0800
committerCommit bot <commit-bot@chromium.org>2016-03-02 13:55:33 +0000
commit8cdf034791388299f18fba186f2941313320b706 (patch)
tree48c9929b48abb9d2a691b14c3e401b5c504b9e30 /remoting/remoting.gyp
parentd8f28037ba276d37296c153ee78346af5e190f4e (diff)
downloadchromium_src-8cdf034791388299f18fba186f2941313320b706.zip
chromium_src-8cdf034791388299f18fba186f2941313320b706.tar.gz
chromium_src-8cdf034791388299f18fba186f2941313320b706.tar.bz2
Move libvpx_new to libvpx
The move to libvpx_new happened before M47 (landed in 2524, M47 branch was 2526): crbug.com/481034 https://codereview.chromium.org/1323333002 Clients which try to transition directly between the tree after this change and before the previous move will end up in a very broken state. Now it is 6 months later and M48 is stable so is unlikely that a client would check out the old code at all, much less try to transition directly between the two versions. Leave a compatibility layer for targets which need to be updated out of band (webrtc, libyuv) Review URL: https://codereview.chromium.org/1734613003 Cr-Commit-Position: refs/heads/master@{#378739}
Diffstat (limited to 'remoting/remoting.gyp')
-rw-r--r--remoting/remoting.gyp2
1 files changed, 1 insertions, 1 deletions
diff --git a/remoting/remoting.gyp b/remoting/remoting.gyp
index e45e264..7905776 100644
--- a/remoting/remoting.gyp
+++ b/remoting/remoting.gyp
@@ -200,7 +200,7 @@
'../media/media.gyp:media',
'../media/media.gyp:shared_memory_support',
'../net/net.gyp:net',
- '../third_party/libvpx_new/libvpx.gyp:libvpx_new',
+ '../third_party/libvpx/libvpx.gyp:libvpx',
'../third_party/libyuv/libyuv.gyp:libyuv',
'../third_party/opus/opus.gyp:opus',
'../third_party/protobuf/protobuf.gyp:protobuf_lite',