>I assume there is a champion for the Win32 version (Theodore?).
Champion may be a bit of a strong word, but yes I'm still on board and about
80% done updating the Win32 build files.
I'm figuring I'll have everything building in about a week.
>If not, I could handle the win32 updates, assuming win32 CVS client
>works also for the other direction.
I've not had good luck with the Win32 native CVS - I use the Cygwin port myself
(but then 'cause I like bash more anyway).
>My current local version for Win32/FX contains some "GLAPIENTRY" fixes
>in the api files and some other "calling convention" stuff. It is also
>hacked to include X86 assembly files, but I am not yet sure how to
>get that into distribution (I used nasm to compile it)
If you'd ship me your changed files directly it might shave some time. I can
also work on converting the nasm into MSVC inline asm so that people won't have
to find and install nasm. It's possible I won't be able to as the VC inline
asm isn't the greatest in the world, but we'll see if I can.
[Keith Whitwell stated...]
>I think the format Josh is using in the x86 directory is a pretty good
>idea. Do you see any problems with this on windows?
I don't see a huge problem with it, but there is a pre-existing Win32 subdir
structure - it just predates the CVS repository. Currently it has no code, only
project files (MSVC DSP/DSW and makefiles), and has project files for *all*
components (Mesa, GLU, GLUT, all demos, samples, and test progs), and it's a
nontrivial amount of junk so I can't say I'm *wholly* in favor of putting it
under 'src'. I have had the nagging feeling that it may have been too much in
one place though, so once I get the stuff built and working I'll see about
rearranging it more cleanly and putting the various project stuffs around in a
more distributed layout.
-Ted
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
