tag 597019 wontfix
thanks
Michel Dänzer daen...@debian.org (16/09/2010):
I'm leaning towards considering libgl1-mesa-swx11-dev shipping
libGL.a a mistake rather than libgl1-mesa-dev not shipping one.
Looks sane to me, I'll probably do so in a later upload.
Tagging this bug wontfix for now.
On Wed, Sep 15, 2010 at 18:52:26 -0400, Chris King wrote:
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?
Is there a reason why it should?
Cheers,
On Thu, Sep 16, 2010 at 5:07 AM, Julien Cristau jcris...@debian.org 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
On Thu, Sep 16, 2010 at 11:24 AM, Chris King colander...@gmail.com 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,
On Don, 2010-09-16 at 11:24 -0400, Chris King wrote:
On Thu, Sep 16, 2010 at 5:07 AM, Julien Cristau jcris...@debian.org 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
2010/9/16 Michel Dänzer daen...@debian.org:
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
On Don, 2010-09-16 at 11:43 -0400, Chris King wrote:
2010/9/16 Michel Dänzer daen...@debian.org:
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
2010/9/16 Michel Dänzer daen...@debian.org:
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
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:
9 matches
Mail list logo
