On Sun, 6 Feb 2005 16:45:00 -0500, Daniel Phillips <[EMAIL PROTECTED]> wrote: > What is wrong with gcc for this? You probably won't be doing too much > forms design.
I am new to graphics driver development on the Windows platform so I might not be on the right track (so far I have only created a framebuffer driver for my old radeon card) - I am however pretty sure that we need the DDK for accessing the appropriate Windows kernel headers, and I am also quite sure that gcc, will not compile code that will integrate cleanly into the Windows kernel. But I might be wrong here. >From my experience, using CygWIN or MinGW to do Windows development is less than optimal (a real pain may be another way to put it) - the native Windows tools works much better. > Auto tools... let me remark that Mesa is a joy to configure and build, > and does not use autoconf/automake. In fact, they used to use it but > had problems so they switched to conventional make. I don't violently > object to auto tools so long as somebody else puts in the time to make > them work properly. I also don't see that they buy a lot. > > From the Mesa docs: > > "Mesa uses a rather conventional Makefile system. A GNU > autoconf/automake system used to be included, but was discarded in Mesa > 5.1 because: > > * It seldom worked on IRIX, Solaris, AIX, etc. > * It was very compilicated > * Nobody maintained it > * libtool was just too weird" I know - it was not my suggestion to use these, I was just wondering how Nvidia have done it (anyway I will check the Nvidia Linux install code out one of these days) - for our part it will not be a problem because the driver will just go into the Xorg/kernel source tree. So no need to worry about maintaining autotools (I however seams to remember that Xorg is working on refactoring the source tree to work with auto tools - or is that just me). Regards. Lars Roland _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
