From:	Gecko23 <gk_2345 AT my-deja DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Stuck in a GLUT!
Date:	Mon, 04 Dec 2000 16:13:07 GMT
Organization:	Deja.com - Before you buy.
Lines:	58
Message-ID:	<90gfqa$456$1@nnrp1.deja.com>
References:	<xJTV5.4713$jd2 DOT 65573 AT news6-win DOT server DOT ntlworld DOT com>
NNTP-Posting-Host:	63.52.227.218
X-Article-Creation-Date:	Mon Dec 04 16:13:07 2000 GMT
X-Http-User-Agent:	Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt)
X-Http-Proxy:	1.0 x53.deja.com:80 (Squid/1.1.22) for client 63.52.227.218
X-MyDeja-Info:	XMYDJUIDgk_2345
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In article <xJTV5.4713$jd2 DOT 65573 AT news6-win DOT server DOT ntlworld DOT com>,
  "aGGa" <agga AT agga[remove me]net.id[& me]ps.co.uk> wrote:
>
> 1. I have downloaded OpenGL header files and libraries from various
sources
> (MS, SGI, Mesa, and those that came with Mingw32). Which of these do
i want
> to be using, because they presumably aren't compatible with each
other.

Use MS, it will take advantage of vendor supplied ICDs if present (i.e.
hardware acceleration). I have a S3 Savage4 based card in my PC and it
performs very well with MS.

The SGI version is very complete, but is also very old and hasn't been
updated for a very long time (years). Mesa has some perks, but unless
you are using a 3dfx based card, won't give you hardware acceleration
last I knew, and is generally slower than either the MS or SGI
implementations IMHO. (Not to mention it is a mainly *nix project, and
windows compatibility isn't the developer's priority)

>
> 2. Libraries have got me confused: All these downloads contain files
with
> the *.lib extension and yet the Mingw32 lib directory contains files
with
> the *.a extension. Do I rename these *.lib files to *.a ?

No. LIB and A are entirely different library formats. VC++ will accept
either, but MingW knows only A. There are libraries in the correct
format, as well as info and tools for generating them yourself
available. Not to mention knowledgeable people available on the MingW
mailing list who have dealt with such things. (see below also...)

>
> 3. Why is the Mingw32 distribution incomplete? There are no gl.h or
glu.h
> files there ...
gl.h and glu.h are *not* part of the windows API. Therefor they are not
in the MingW distro. Simple as that. Not to mention that the win api
included with MingW is mostly complete, but is still being worked on.
(It is illegal to simply rip MS's headers from VC++ and re-distribute
them after all, these are being re-created from other docs.)

>
> There are loads more questions but i'll leave it at that for the
>moment ;-)

If you have more questions, the best place to ask them is the MingW
mailing list hosted on EGroups (www.egroups.com). Many of the
developers and users of MingW started here, and continue to hang out
here, but this is comp.os.msdos.djgpp after all.

Anyways, good luck.


Sent via Deja.com http://www.deja.com/
Before you buy.

- Raw text -