Switch libvpx from static_library to none

Switch libvpx from static_library to none

Follow in the vein of BUILD.gn switch to group()
https://codereview.chromium.org/1364033003

R=blundell@chromium.org
BUG=534943
Committed: https://chromium.googlesource.com/chromium/deps/libvpx/+/b33794b9132c8c1722206d6676c37177ccbaef2e

[Johann, 2015-09-24 16:33:06]

gclient --runhooks and a build pass locally. I looked briefly for alternatives
to dependencies and direct_dependent_settings (the way gn has public_deps and
public_config) but didn't notice anything (export_dependent_settings maybe? but
I was looking for a modifier to dependencies)

[blundell, 2015-09-24 18:53:16]

Thanks for following up here! I would run a clobber tryjob ("git cl try -c") in
Chromium before you roll DEPS to bring in this change just to make absolutely
sure that it's kosher. I'm pretty sure that it should be (and in fact should be
safer than what's there now).

https://codereview.chromium.org/1365973002/diff/1/libvpx.gyp
File libvpx.gyp (right):

https://codereview.chromium.org/1365973002/diff/1/libvpx.gyp#newcode14
libvpx.gyp:14: 'direct_dependent_settings': {
Assuming that libvpx_new has the same the same include_dirs set as here, the
better choice is indeed:

'export_dependent_settings': [
  'blablabla/libpvpx.gyp:libvpx_new',
],

[Johann, 2015-09-24 19:17:30]

Testing locally now. Need to land this and set up the roll to run trybots.

https://codereview.chromium.org/1365973002/diff/1/libvpx.gyp
File libvpx.gyp (right):

https://codereview.chromium.org/1365973002/diff/1/libvpx.gyp#newcode14
libvpx.gyp:14: 'direct_dependent_settings': {
On 2015/09/24 18:53:16, blundell wrote:
> Assuming that libvpx_new has the same the same include_dirs set as here, the
> better choice is indeed:
> 
> 'export_dependent_settings': [
>   'blablabla/libpvpx.gyp:libvpx_new',
> ],

It looks like cc/cc.gyp has a similar config, with skia in both dependencies and
export_dependent_settings so I think I got it OK

[Johann, 2015-09-24 19:28:33]

On 2015/09/24 18:53:16, blundell wrote:
> Thanks for following up here! I would run a clobber tryjob ("git cl try -c")
in
> Chromium before you roll DEPS to bring in this change just to make absolutely
> sure that it's kosher. I'm pretty sure that it should be (and in fact should
be
> safer than what's there now).

I should upload an empty/trivial change, run 'git cl try -c', and then upload
the DEPS change and run a try again? Or run 'git cl try -c' as part of the DEPS
change?

[blundell, 2015-09-24 19:36:52]

LGTM

Run the clobber tryjob on the CL rolling DEPS...that will ensure that all the
bots do a clean build of that CL.

[Johann, 2015-09-24 19:51:13]

Committed patchset #2 (id:20001) manually as
b33794b9132c8c1722206d6676c37177ccbaef2e.