mojo: add GL_APIENTRY

mojo: add GL_APIENTRY

mojo changes to make everyone use the same calling convention on windows

see: https://codereview.chromium.org/1260253003

R=jamesr@chromium.org

Committed: https://chromium.googlesource.com/external/mojo/+/d17aba5deb88a59cc9ada00c1f6d26e353778d06

[hendrikw, 2015-07-31 22:31:35]

hendrikw@chromium.org changed reviewers:
+ jamesr@chromium.org

[hendrikw, 2015-07-31 22:31:35]

PTAL, thanks!

[jamesr, 2015-08-03 17:42:07]

lgtm

[jamesr, 2015-08-03 17:42:48]

There's no CQ here, I can land this patch for you.

[hendrikw, 2015-08-03 17:49:41]

On 2015/08/03 17:42:48, jamesr wrote:
> There's no CQ here, I can land this patch for you.

ok, cool, thanks

Please hold off on landing for a bit, I want to try to land chrome's changes
around the same time and I'm still waiting on a couple lgtm's.

[jamesr, 2015-08-03 18:05:40]

The mojo roll is decoupled, so this can land at any point relative to chrome
changes.  This patch landing won't impact chrome code until someone does an
explicit roll.

[hendrikw, 2015-08-03 18:07:48]

On 2015/08/03 18:05:40, jamesr wrote:
> The mojo roll is decoupled, so this can land at any point relative to chrome
> changes.  This patch landing won't impact chrome code until someone does an
> explicit roll.

yeah, I realize that, I wanted to avoid the chance that someone rolls this
before I get the other cl in, but if you don't think that will happen, please go
ahead and land, thanks!

[hendrikw, 2015-08-06 20:10:36]

On 2015/08/03 18:07:48, hendrikw wrote:
> On 2015/08/03 18:05:40, jamesr wrote:
> > The mojo roll is decoupled, so this can land at any point relative to chrome
> > changes.  This patch landing won't impact chrome code until someone does an
> > explicit roll.
> 
> yeah, I realize that, I wanted to avoid the chance that someone rolls this
> before I get the other cl in, but if you don't think that will happen, please
go
> ahead and land, thanks!

Hi jamesr, the other cl has landed, please land this patch when you get a
chance, thanks!

[jamesr, 2015-08-11 00:25:23]

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

[jamesr, 2015-08-11 00:25:34]

On 2015/08/06 at 20:10:36, hendrikw wrote:
> On 2015/08/03 18:07:48, hendrikw wrote:
> > On 2015/08/03 18:05:40, jamesr wrote:
> > > The mojo roll is decoupled, so this can land at any point relative to
chrome
> > > changes.  This patch landing won't impact chrome code until someone does
an
> > > explicit roll.
> > 
> > yeah, I realize that, I wanted to avoid the chance that someone rolls this
> > before I get the other cl in, but if you don't think that will happen,
please go
> > ahead and land, thanks!
> 
> Hi jamesr, the other cl has landed, please land this patch when you get a
chance, thanks!

Sorry for the delay, this is in now.