[Mesa-dev] Questions regarding KHR_debug for OpenGL ES
Timothy Arceri
t_arceri at yahoo.com.au
Fri Mar 28 01:29:34 PDT 2014
On Fri, 2014-03-28 at 19:22 +1100, Timothy Arceri wrote:
> On Wed, 2014-03-26 at 16:27 -0700, Felipe Tonello wrote:
> > Hi Timothy,
> >
> > On Sun, Mar 23, 2014 at 2:11 PM, Timothy Arceri <t_arceri at yahoo.com.au> wrote:
> > > On Mon, 2014-03-17 at 11:42 -0700, Felipe Tonello wrote:
> > >> Hi all,
> > >>
> > >> I'm working on the KHR_debug for OpenGL ES junior job. I recently
> > >> submitted patches to allow the piglit tests to be enabled in GLES
> > >> contexts as well.
> > >> Now I want to work on the src/mapi/glapi/gen/es_EXT.xml file. Recently
> > >> I saw a patch that moved the KHR_debug extension to a include type of
> > >> file.
> > >>
> > >> My question is: How can I reuse this file but change the functions
> > >> definitions to add the KHR suffix?
> > >
> > > Hi Felipe,
> > >
> > > You need to use the alias attribute. Take a look at ARB_debug_output.xml
> > > basically you will need to do the same thing in the es_EXT.xml file but
> > > using the KHR suffix rather than ARB. I don't think there is anyway to
> > > avoid the obvious duplications here (someone please correct me if I'm
> > > wrong).
> > >
> > > Tim
> > >
> >
> > Where should I define GLDEBUGPROCKHR? I tried gl_and_es_API.xml under
> > <category name="es2.0"> but when I compile I get that the compiler
> > cannot find GLDEBUGPROCKHR type name.
> >
> > Any idea?
>
> I'm not 100% sure where the es stuff should go
After a second look I think it might need to go in
<category name="es1.0"> as per Ian's instructions on the wiki page
"advertise GL_KHR_debug in ES1 and ES2 contexts."
> but I think you need to
> add it like this:
>
> <type name="DEBUGPROCKHR" size="4" pointer="true"/>
>
> i.e try removing GL
>
> Does that help?
>
> Tim
>
> >
> > BR
> >
> > Felipe
>
>
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/mesa-dev
More information about the mesa-dev
mailing list