Couple things. First, if we're going to start autogenerating headers, can we do GL API first? I've got a handful of patches against those Python scripts, and I can always sit down in a couple days and bang out the rest of it.
(While we're at it, since we're doomed to bring it up every couple months, can we do automake? Please?) For coding conventions, sorry for 4-space tabs in r300 and radeon. I don't intend to change it though. If coding conventions are SERIOUS BUSINESS, then can we just write down indent rules? Finally, there are almost certainly already out-of-tree drivers and state trackers based on 0.1 and 0.2 "versions" of the API. Why wasn't it a priority to version the API before? ~ C. On Fri, Jan 1, 2010 at 3:29 AM, Thomas Hellstrom <thellst...@vmware.com> wrote: > Keith Whitwell wrote: >> Luca, >> >> This is an impressive body of work. I want to give Jose a chance to >> review the EGL/GLX extensions before pushing, but in the meantime I hope >> it's ok if I make a couple of quick suggestions/requests: >> >> Firstly, we're going to be evolving the TGSI instruction set a fair bit >> over the coming months to catch up with newer GLSL versions, CL, etc. >> >From that point of view, it would be preferable if the code you've added >> in uureg.h could be automatically regenerated after TGSI changes. I see >> you've got some python in the comments showing how you built the file in >> the first place -- would it be possible to extract that to an actual >> script that the build system can use to regenerate uureg.h on TGSI >> changes? I'm mainly thinking about automatically tracking new >> instructions, I guess. >> >> > One implication of exposing the Gallium API in this way would probably > be that people start to > develop out-of-tree applications, and that means the API needs to be > versioned..... > > /Thomas > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Mesa3d-dev mailing list > Mesa3d-dev@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mesa3d-dev > -- Only fools are easily impressed by what is only barely beyond their reach. ~ Unknown Corbin Simpson <mostawesomed...@gmail.com> ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
