Message-ID: From: George Kinney To: djgpp AT delorie DOT com Subject: Re: MESA3D compiling problem Date: Tue, 30 May 2000 14:21:40 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFCA63.E681C2E0" Reply-To: djgpp AT delorie DOT com This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFCA63.E681C2E0 Content-Type: text/plain >B'cause Brian Paul said that Mesa's dos drivers needs some >substansial works I decided to quit trying to compile Mesa and >switch to MGL instead. FWIW, Mesa 3.0 with Berhard Tschirren's Allegro driver compiles out of the box, and Mesa 3.2 works with some very slight patching. (the only thing that has changed from the driver's point of view is that some of the sources have been renamed, and new ones have been added.) It comes with a minimal GLUT that compiles practically everthing available with the distro. (As well as 80-90% of the sample GL sources I was able to find on the net.) Also, Mesa will compile into the OS (off screen) driver, (just gotta type 'sh configure' then 'make' and when you create a rendering context, just pass a linear buffer big enough to hold the pixel data (like an allegro bitmap, i.e. bmp->line[0]) and off you go. Only downside is you then have no GLUT. It surprises me that there have been so many threads in this group over the horrors of Mesa and DJGPP when it is really quite easy. (esp. thanks to Mr. Tschirren's work on 3.0 and earlier.) (For the curious, I use djdev2.03 bnu2952 and gcc2952 with locally compiled bash, sh-utils, and fil-utils just to make sure they were built with the latest stuff.) ------_=_NextPart_001_01BFCA63.E681C2E0 Content-Type: text/html Re: MESA3D compiling problem

>B'cause Brian Paul said that Mesa's dos drivers needs some
>substansial works I decided to quit trying to compile Mesa and
>switch to MGL instead.

FWIW, Mesa 3.0 with Berhard Tschirren's Allegro driver compiles
out of the box, and Mesa 3.2 works with some very slight patching.
(the only thing that has changed from the driver's point of view is that
some of the sources have been renamed, and new ones have been added.)

It comes with a minimal GLUT that compiles practically everthing
available with the distro. (As well as 80-90% of the sample GL sources I
was able to find on the net.)

Also, Mesa will compile into the OS (off screen) driver, (just gotta type
'sh configure' then 'make' and when you create a rendering context,
just pass a linear buffer big enough to hold the pixel data (like an
allegro bitmap, i.e. bmp->line[0]) and off you go. Only downside is
you then have no GLUT.

It surprises me that there have been so many threads in this group over
the horrors of Mesa and DJGPP when it is really quite easy. (esp. thanks to
Mr. Tschirren's work on 3.0 and earlier.)

(For the curious, I use djdev2.03 bnu2952 and gcc2952 with locally compiled
bash, sh-utils, and fil-utils just to make sure they were built with the latest
stuff.)

------_=_NextPart_001_01BFCA63.E681C2E0--