On Mon, 14 Feb 2000, Brett Johnson wrote:
> Date: Mon, 14 Feb 2000 14:26:08 -0700
> From: Brett Johnson <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: [oglbase-discuss] Library dependencies
>
> Brian Paul wrote:
> >
> > Brett Johnson wrote:
> > > For example, if an app compiles against the Mesa libs, it doesn't
[...]
> > app link command. Listing the same library twice (even if once
> > is an indirect occurance) shouldn't cause an error.
>
> It doesn't cause an error. All I said was that many apps won't bother
> to resolve their own dependencies this way. If the app works without
> resolving them (since all the symbols are resolved through Mesa, and
> everything works just fine under Mesa), it's pretty easy for the ISV
> to not bother tracking down all of the symbols they "should" be
> resolving directly on their own link line. It's particularly easy if
> the ISV is small, and doesn't have the resources to test the app on
> a wide variety of libGL implementations.
>
Hmm. I though the whole point of the Linux/OGL base was to create
that compatibility... Certainly our OGL only links what it specifically
needs... An easy way to find these types of things is simply (in your
case) link a static version of Mesa into your app... The linker will tell
you what you need ;-)
> > Also, a number of them, like Xmu, XI, Xt, are
> > only needed because of GLUT.
>
> That may be true, but they're still included as transitive links in
> Mesa's libGL.so.
I don't think we should rely on that... I'm not really sure why
Mesa would be interested in ICE/SM (unless they are using Xt in there
somewhere). We certainly aren't ;-)
> As a result, many applications that are compiled
> against Mesa won't run against any other libGL unless the other libGL
> also provides transitive links to Xmu, Xi and Xt.
>
Well, I've tested a few(!) apps, from artstream to quake 3, and
have not seen any problems. The only problems I've seen is when
applications (like an early beta of Artstream) required a specific Mesa
extension (OSMesaCreateContext). That is the only case I've seen where
there was a failure - and they've since fixed it...
--
Jon Trulson work: mailto:[EMAIL PROTECTED], home: mailto:[EMAIL PROTECTED]
Xi Graphics, Inc. http://www.xig.com
ID: 1A9A2B09, FP: C23F328A721264E7 B6188192EC733962
PGP keys at http://radscan.com/PGPKeys.txt
#include <stddisclaimer.h>
You talk like a Ferengi.
