Date: Wed, 31 May 2000 09:37:05 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: George Kinney <GKinney AT nextransport DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: MESA3D compiling problem
In-Reply-To: <DB85AFBE7C0DD311BF260004ACB80BFC01F9CE@nex_server.nextransport.com>
Message-ID: <Pine.SUN.3.91.1000531093640.8817D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 30 May 2000, George Kinney wrote:

> Also, Mesa will compile into the OS (off screen) driver, (just gotta type 
> 'sh configure' then 'make' and when you create a rendering context, 
[snip]
> 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.

Well, perhaps that's a sign that it's not that easy, after all ;-).
There *are* quite a few packages that support DJGPP without generating
too many threads here, you know.

For example, "sh configure" might not be something most users would
cough out as their first guess.  Either providing a batch file with a
catchy name, like djbuild.bat, or some README.djgpp that explains how
to go (or both) might improve things and cut down the FAQs.  Making
sure the ``slight patching'' required to build Mesa 3.2 gets into the
official distribution might also help.