glapi_x86.S glx86asm.py
Title: glapi_x86.S glx86asm.py according to its headline glapi_x86.S was generated by the script glx86asm.py - its just that i cannot find that script in the XFree86 sources. Any hints? -Alex.
Re: glapi_x86.S glx86asm.py
On Thu, 30 Jan 2003, Alexander Stohr wrote: according to its headline glapi_x86.S was generated by the script glx86asm.py - its just that i cannot find that script in the XFree86 sources. Any hints? From CVS/XFree86/xc/extras/Mesa/bin/Attic/glx86asm.py,v revision 1.2 date: 2000/12/07 16:12:47; author: dawes; state: dead; lines: +0 -0 Remove from the trunk the Mesa files that aren't needed. Latest entry in cvs log of c/extras/Mesa/src/X86/glapi_x86.S revision 1.7 date: 2002/09/09 21:07:33; author: dawes; state: Exp; lines: +1 -1 Mesa 4.0.2 merge (So the script glx86asm.py was removed after glapi_x86.S last changed, which is a good sign). -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: glapi_x86.S glx86asm.py
On Thu, 30 Jan 2003, Alexander Stohr wrote: From CVS/XFree86/xc/extras/Mesa/bin/Attic/glx86asm.py,v really? hmm, if the respective API listing ever changes or extends it might be simpler to use an existing script and then submitting the results than to perform error prone copy and paste operations on the results. i mean thats the reason why (possibly Brian Paul) added such a highly descriptive headline about that file beeing a generated one. The file is probably still present in the upstream Mesa source. The Mesa source in the XFree86 tree is just a copy, which appears to have had some of the non-relevent stuff cleaned out. Stuart Stuart R. Anderson [EMAIL PROTECTED] Network Software Engineering http://www.netsweng.com/ 1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F BD03 0A62 E534 37A7 9149 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: glapi_x86.S glx86asm.py
Alexander Stohr wrote: From CVS/XFree86/xc/extras/Mesa/bin/Attic/glx86asm.py,v revision 1.2 date: 2000/12/07 16:12:47; author: dawes; state: dead; lines: +0 -0 Remove from the trunk the Mesa files that aren't needed. Latest entry in cvs log of c/extras/Mesa/src/X86/glapi_x86.S revision 1.7 date: 2002/09/09 21:07:33; author: dawes; state: Exp; lines: +1 -1 Mesa 4.0.2 merge (So the script glx86asm.py was removed after glapi_x86.S last changed, which is a good sign). really? hmm, if the respective API listing ever changes or extends it might be simpler to use an existing script and then submitting the results than to perform error prone copy and paste operations on the results. You'd have to ask Brian to be sure, but I believe the intention is that if the interface ever changes, a new .S file be generated in the Mesa tree and imported to the XFree86 DRI trees. There should never be a case where the .S file would change in XFree86 and not change in Mesa. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: glapi_x86.S glx86asm.py
You'd have to ask Brian to be sure, but I believe the intention is that if the interface ever changes, a new .S file be generated in the Mesa tree and imported to the XFree86 DRI trees. There should never be a case where the .S file would change in XFree86 and not change in Mesa. agreed, a rational method of doing it. i just didnt remeber that libGL and Mesa implementation are maintained elsewhere and are merely contributed parts. -Alex. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
