Don't #define snprintf in VS 2015 or higher.

Don't #define snprintf in VS 2015 or higher.

In VS 2015 and higher snprintf is supplied and therefore vsnprintf
doesn't need to be defined. This also avoids problems caused by
_snprintf being different from snprintf.

This fixes a build break with VS 2015 and improves security.

R=tomfinegan@chromium.org
BUG=440500
Committed: https://chromium.googlesource.com/chromium/deps/libvpx/+/0816cf21b0f04c1d2cf86b4e3d120a49e4ac8fa6

[brucedawson, 2015-04-14 23:20:07]

brucedawson@chromium.org changed reviewers:
+ tomfinegan@chromium.org

[Johann, 2015-04-15 13:33:15]

LGTM

https://gerrit.chromium.org/gerrit/74359

[brucedawson, 2015-04-15 15:59:16]

The CQ bit was checked by brucedawson@chromium.org

[commit-bot: I haz the power, 2015-04-15 16:01:54]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-04-15 16:01:55]

Commit queue rejected this change because it did not recognize the base URL.
Please commit your change manually.

[Johann, 2015-04-15 16:03:46]

libvpx is in a weird location in the chromium tree. try:
$ git cl land

[Johann, 2015-04-15 16:05:57]

On 2015/04/15 16:03:46, Johann wrote:
> libvpx is in a weird location in the chromium tree. try:
> $ git cl land

Once it is merged, it needs to roll to DEPS to have any effect:
https://codereview.chromium.org/1068113002/

[Tom Finegan, 2015-04-15 16:46:48]

On 2015/04/15 16:05:57, Johann wrote:
> On 2015/04/15 16:03:46, Johann wrote:
> > libvpx is in a weird location in the chromium tree. try:
> > $ git cl land
> 
> Once it is merged, it needs to roll to DEPS to have any effect:
> https://codereview.chromium.org/1068113002/

Should probably land this upstream-- we'll need it in the libvpx repo as well
when we start supporting VS2015. Otoh this is super simple and a build fix, so
both?

lgtm

[Johann, 2015-04-15 20:38:10]

Committed patchset #1 (id:1) manually as
0816cf21b0f04c1d2cf86b4e3d120a49e4ac8fa6 (presubmit successful).