Not easily. Although updating the file quarterly would hrlp prevent out of date copies of the xml file from being an issue. ( or when a patch sequence calls for updating the file ) On Jun 13, 2014 10:43 AM, "Dylan Baker" <[email protected]> wrote:
> Is there an obvious way for us to tell when our version of gl.xml has > drifted > out of date with the upstream khronos version? > > On Friday, June 13, 2014 07:44:32 AM Chad Versace wrote: > > Import revision 26792 on 2014-05-22 from > > ( > https://cvs.khronos.org/svn/repos/ogl/trunk/doc/registry/public/api/gl.xml > ) > > . > > > > I'm importing the Khronox XML because I want to generate piglit-dispatch > > code from it rather than scraping GL headers and unmaintained *.spec > > files. > > > > Signed-off-by: Chad Versace <[email protected]> > > --- > > > > Full patch redacted due to size. > > > > registry/gl.xml | 42166 > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, > > 42166 insertions(+) > > create mode 100644 registry/gl.xml > > > > diff --git a/registry/gl.xml b/registry/gl.xml > > new file mode 100644 > > index 0000000..30e8d9f > > --- /dev/null > > +++ b/registry/gl.xml > > @@ -0,0 +1,42166 @@ > > +<?xml version="1.0" encoding="UTF-8"?> > > +<registry> > > + <comment> > > +Copyright (c) 2013-2014 The Khronos Group Inc. > > + > > +Permission is hereby granted, free of charge, to any person obtaining a > > +copy of this software and/or associated documentation files (the > > +"Materials"), to deal in the Materials without restriction, including > > +without limitation the rights to use, copy, modify, merge, publish, > > +distribute, sublicense, and/or sell copies of the Materials, and to > > +permit persons to whom the Materials are furnished to do so, subject to > > +the following conditions: > > + > > +The above copyright notice and this permission notice shall be included > > +in all copies or substantial portions of the Materials. > > + > > +THE MATERIALS ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, > > +EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF > > +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. > > +IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY > > +CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, > > +TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE > > +MATERIALS OR THE USE OR OTHER DEALINGS IN THE MATERIALS. > > + > > +------------------------------------------------------------------------ > > + > > +This file, gl.xml, is the OpenGL and OpenGL API Registry. The older > > +".spec" file format has been retired and will no longer be updated with > > +new extensions and API versions. The canonical version of the registry, > > +together with documentation, schema, and Python generator scripts used > > +to generate C header files for OpenGL and OpenGL ES, can always be found > > +in the Khronos Registry at > > + http://www.opengl.org/registry/ > > + </comment> > > _______________________________________________ > > Piglit mailing list > > [email protected] > > http://lists.freedesktop.org/mailman/listinfo/piglit > > _______________________________________________ > Piglit mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/piglit > >
_______________________________________________ Piglit mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/piglit
