Update the libvpx GN build files with the cpu_arch -> current_cpu change.

Update the libvpx GN build files with the cpu_arch -> current_cpu change.

This updates the build to remove references to the newly deprecated
variables.

R=johannkoenig@google.com, tomfinegan@chromium.org
BUG=344767
Committed: https://chromium.googlesource.com/chromium/deps/libvpx/+/6a19aa1e1f636f40eda73a1378586e0b514fb9cd

[Dirk Pranke, 2015-02-20 20:26:38]

Hi Tom,

Can you take a look at this and, assuming it looks okay to you, either land this
for me or tell me how to land it and help me know what I need to do to get it
rolled into Chromium?

[Johann, 2015-02-20 21:30:38]

johannkoenig@google.com changed reviewers:
+ johannkoenig@google.com

[Johann, 2015-02-20 21:30:39]

LGTM

should the bug be just the number, instead of the full url?

To roll, you need to make a change that looks like this:
https://codereview.chromium.org/942533004/

Let me know if any part of that is not clear. This is the only change since that
roll, so you only need to link to this change in the message.

[Dirk Pranke, 2015-02-20 21:51:03]

On 2015/02/20 21:30:39, Johann wrote:
> should the bug be just the number, instead of the full url?

Wasn't sure if you tracked vpx bugs in a different repo or not ... fixed.

[Dirk Pranke, 2015-02-20 21:52:39]

The CQ bit was checked by dpranke@chromium.org

[Johann, 2015-02-20 21:53:25]

On 2015/02/20 21:51:03, Dirk Pranke wrote:
> On 2015/02/20 21:30:39, Johann wrote:
> > should the bug be just the number, instead of the full url?
> 
> Wasn't sure if you tracked vpx bugs in a different repo or not ... fixed.

Only for issues that get uploaded to the upstream repo. Anything here goes to
the chromium bug tracker.

[Dirk Pranke, 2015-02-20 21:55:12]

The CQ bit was unchecked by dpranke@chromium.org

[Dirk Pranke, 2015-02-20 21:55:55]

How would one get this patch committed? I don't know that I'm a committer on
this repo, nor whether I need to run try jobs (I don't think there's a CQ ...)

[Johann, 2015-02-20 21:57:10]

On 2015/02/20 21:55:55, Dirk Pranke wrote:
> How would one get this patch committed? I don't know that I'm a committer on
> this repo, nor whether I need to run try jobs (I don't think there's a CQ ...)

Ahh, sorry:
git cl land

[Johann, 2015-02-20 21:58:16]

On 2015/02/20 21:57:10, Johann wrote:
> On 2015/02/20 21:55:55, Dirk Pranke wrote:
> > How would one get this patch committed? I don't know that I'm a committer on
> > this repo, nor whether I need to run try jobs (I don't think there's a CQ
...)
> 
> Ahh, sorry:
> git cl land

As long as you're a chromium committer it will work. If you're only partial like
me, you need an LGTM from a real one (like Tom). The repo is more owned by
chromium than by webm.

[Dirk Pranke, 2015-02-20 21:59:46]

Committed patchset #1 (id:1) manually as
6a19aa1e1f636f40eda73a1378586e0b514fb9cd (presubmit successful).

[Dirk Pranke, 2015-02-20 22:00:31]

On 2015/02/20 21:58:16, Johann wrote:
> On 2015/02/20 21:57:10, Johann wrote:
> > On 2015/02/20 21:55:55, Dirk Pranke wrote:
> > > How would one get this patch committed? I don't know that I'm a committer
on
> > > this repo, nor whether I need to run try jobs (I don't think there's a CQ
> ...)
> > 
> > Ahh, sorry:
> > git cl land
> 
> As long as you're a chromium committer it will work. If you're only partial
like
> me, you need an LGTM from a real one (like Tom). The repo is more owned by
> chromium than by webm.

Got it, thanks!