2010/9/16 Michel Dänzer :
>> Why, may I ask? Because there are multiple implementations of libGL?
>
> Exactly.
OK, that makes sense enough. Thanks.
> It occurred to me that there might also be a way to make symbols you
> don't want to wrap be automagically resolved from the wrapped libGL, but
>
2010/9/16 Michel Dänzer :
> I'm leaning towards considering libgl1-mesa-swx11-dev shipping libGL.a a
> mistake rather than libgl1-mesa-dev not shipping one.
Why, may I ask? Because there are multiple implementations of libGL?
> The downside is that the wrapper becomes specific to the libGL linke
On Thu, Sep 16, 2010 at 11:24 AM, Chris King wrote:
> Most other -dev packages in Debian provide static libraries, since
> they're very useful for testing.
Specifically:
http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-static
--
To UNSUBSCRIBE, email to de
On Thu, Sep 16, 2010 at 5:07 AM, Julien Cristau wrote:
> Is there a reason why it should?
Yes, for anybody who wants to statically link the GLX OpenGL library
:) Most other -dev packages in Debian provide static libraries, since
they're very useful for testing.
My specific use case is in making
Package: libgl1-mesa-dev
Version: 7.7.1-2
Severity: normal
Title says it all -- the only libGL.a available is in libgl1-mesa-swx11-dev,
which uses software rendering. Maybe there should exist a
libgl1-mesa-glx-dev? Is there a reason why it can't?
-- System Information:
Debian Release: squeeze/
5 matches
Mail list logo
