On 01/03/2013 01:31 PM, Tom Gall wrote:
On Thu, Jan 3, 2013 at 12:48 PM, Chad Versace
chad.vers...@linux.intel.com wrote:
On 01/03/2013 10:00 AM, Tom Gall wrote:
What if instead of parsing over the c source file, why not run the
test with a --tell-me-what-you-support sort of flag?
Spit
On Fri, Jan 4, 2013 at 11:56 AM, Chad Versace
chad.vers...@linux.intel.com wrote:
On 01/03/2013 01:31 PM, Tom Gall wrote:
On Thu, Jan 3, 2013 at 12:48 PM, Chad Versace
chad.vers...@linux.intel.com wrote:
On 01/03/2013 10:00 AM, Tom Gall wrote:
What if instead of parsing over the c source
if you're interested.
Here's what I would like to have in the long term:
1. Waffle needs a facility like piglit-dispatch, so rather than duplicate code
between piglit and waffle, it makes sense to migrate piglit-dispatch to
waffle,
and then extend it to support gles.
2. Piglit-dispatch
to
waffle, and then extend it to support gles.
Exactly!
2. Piglit-dispatch, in its current incarnation, generates its code based on
the files gl.spec, gl.tm, enumext.spec (all published at
www.opengl.org/registry/api/). However, there are some errors and omissions
in those files, so to work
Hi All,
I was looking at some of the piglit-dispatch code experimenting a bit
with the intent to implement it for gles and was wondering where did
the past discussions on this end up?
There is a comment above piglit_dispatch_default_init that mentions
run-time parameters. The Waffle and
