gpu/khronos_conform_support/DEPS - Issue 556333003: Add support for khronos gl-cts using its drawElements apis

Side by Side Diff: gpu/khronos_conform_support/DEPS

Issue 556333003: Add support for khronos gl-cts using its drawElements apis (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Created 6 years, 3 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

OLD	NEW
(Empty)
	1 include_rules = [

	2 "+third_party/khronos_conform",
	piman 2014/09/10 20:12:50 I don't see this directory in either my local chec I don't see this directory in either my local checkout nor any of the DEPS files (either internal or external) U. Artie Eoff 2014/09/10 22:12:59 I guess I'm not certain what this file really does Show quoted text On 2014/09/10 20:12:50, piman (Very slow to review) wrote: > I don't see this directory in either my local checkout nor any of the DEPS files > (either internal or external) I guess I'm not certain what this file really does. But essentially you'll have to clone your licensed version of the khronos conformance sourcecode into that path on your end... using whatever process you've put in place internally to get them. Right? Ken Russell (switch to Gerrit) 2014/09/11 00:03:26 It sounds like someone will have to clone Khronos' Show quoted text On 2014/09/10 22:12:59, uartie wrote: > On 2014/09/10 20:12:50, piman (Very slow to review) wrote: > > I don't see this directory in either my local checkout nor any of the DEPS > files > > (either internal or external) > > I guess I'm not certain what this file really does. But essentially you'll have > to clone your licensed version of the khronos conformance sourcecode into that > path on your end... using whatever process you've put in place internally to get > them. Right? It sounds like someone will have to clone Khronos' GLES3 conformance tests into Chromium's src-internal repository. Frankly, it's quite a pain that the GLES3 conformance tests are not open source. Can you please work within Khronos and try to get these tests open-sourced? I think the value from the tests comes from certification, not simply access to the tests' code. U. Artie Eoff 2014/09/11 01:09:19 That's opening up a can-o-worms ;). A license to Show quoted text On 2014/09/11 00:03:26, Ken Russell wrote: > On 2014/09/10 22:12:59, uartie wrote: > > On 2014/09/10 20:12:50, piman (Very slow to review) wrote: > > > I don't see this directory in either my local checkout nor any of the DEPS > > files > > > (either internal or external) > > > > I guess I'm not certain what this file really does. But essentially you'll > have > > to clone your licensed version of the khronos conformance sourcecode into that > > path on your end... using whatever process you've put in place internally to > get > > them. Right? > > It sounds like someone will have to clone Khronos' GLES3 conformance tests into > Chromium's src-internal repository. Frankly, it's quite a pain that the GLES3 > conformance tests are not open source. Can you please work within Khronos and > try to get these tests open-sourced? I think the value from the tests comes from > certification, not simply access to the tests' code. That's opening up a can-o-worms ;). A license to the Khronos conformance isn't cheap. I'm not trained in the art of lobbying. But I'm sure between the "all of us", someone could persuade them on this proposal. Ken Russell (switch to Gerrit) 2014/09/11 01:25:17 I'll discuss this with some Khronos members and wo Show quoted text On 2014/09/11 01:09:19, uartie wrote: > On 2014/09/11 00:03:26, Ken Russell wrote: > > On 2014/09/10 22:12:59, uartie wrote: > > > On 2014/09/10 20:12:50, piman (Very slow to review) wrote: > > > > I don't see this directory in either my local checkout nor any of the DEPS > > > files > > > > (either internal or external) > > > > > > I guess I'm not certain what this file really does. But essentially you'll > > have > > > to clone your licensed version of the khronos conformance sourcecode into > that > > > path on your end... using whatever process you've put in place internally to > > get > > > them. Right? > > > > It sounds like someone will have to clone Khronos' GLES3 conformance tests > into > > Chromium's src-internal repository. Frankly, it's quite a pain that the GLES3 > > conformance tests are not open source. Can you please work within Khronos and > > try to get these tests open-sourced? I think the value from the tests comes > from > > certification, not simply access to the tests' code. > That's opening up a can-o-worms ;). A license to the Khronos conformance isn't > cheap. I'm not trained in the art of lobbying. But I'm sure between the "all > of us", someone could persuade them on this proposal. I'll discuss this with some Khronos members and would request that you do the same. U. Artie Eoff 2014/09/11 16:50:52 I appreciate that. I'll defer to @chadv on my tea Show quoted text On 2014/09/11 01:25:17, Ken Russell wrote: > On 2014/09/11 01:09:19, uartie wrote: > > On 2014/09/11 00:03:26, Ken Russell wrote: > > > On 2014/09/10 22:12:59, uartie wrote: > > > > On 2014/09/10 20:12:50, piman (Very slow to review) wrote: > > > > > I don't see this directory in either my local checkout nor any of the > DEPS > > > > files > > > > > (either internal or external) > > > > > > > > I guess I'm not certain what this file really does. But essentially > you'll > > > have > > > > to clone your licensed version of the khronos conformance sourcecode into > > that > > > > path on your end... using whatever process you've put in place internally > to > > > get > > > > them. Right? > > > > > > It sounds like someone will have to clone Khronos' GLES3 conformance tests > > into > > > Chromium's src-internal repository. Frankly, it's quite a pain that the > GLES3 > > > conformance tests are not open source. Can you please work within Khronos > and > > > try to get these tests open-sourced? I think the value from the tests comes > > from > > > certification, not simply access to the tests' code. > > That's opening up a can-o-worms ;). A license to the Khronos conformance > isn't > > cheap. I'm not trained in the art of lobbying. But I'm sure between the "all > > of us", someone could persuade them on this proposal. > > I'll discuss this with some Khronos members and would request that you do the > same. I appreciate that. I'll defer to @chadv on my team to bring it up to Khronos.
	3 ]

OLD	NEW