Bug#597019: libgl1-mesa-dev: missing static library (libGL.a)

2011-01-29 Thread Cyril Brulebois
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.

KiBi.


signature.asc
Description: Digital signature


Bug#597019: libgl1-mesa-dev: missing static library (libGL.a)

2010-09-16 Thread Julien Cristau
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,
Julien


signature.asc
Description: Digital signature


Bug#597019: libgl1-mesa-dev: missing static library (libGL.a)

2010-09-16 Thread Chris King
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 case is in making an interposer library.  I need to
re-export hundreds of OpenGL functions unchanged while providing
replacements for a couple; it is possible to do this using dlopen, but
unwieldy since I must write a stub for every function.  Having a
static library available would make this trivial.

- Chris



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#597019: libgl1-mesa-dev: missing static library (libGL.a)

2010-09-16 Thread Chris King
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, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#597019: libgl1-mesa-dev: missing static library (libGL.a)

2010-09-16 Thread Michel Dänzer
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 libraries, since
 they're very useful for testing.

I'm leaning towards considering libgl1-mesa-swx11-dev shipping libGL.a a
mistake rather than libgl1-mesa-dev not shipping one.


 My specific use case is in making an interposer library.  I need to
 re-export hundreds of OpenGL functions unchanged while providing
 replacements for a couple; it is possible to do this using dlopen, but
 unwieldy since I must write a stub for every function.  Having a
 static library available would make this trivial.

The downside is that the wrapper becomes specific to the libGL linked
statically, whereas a dlopen based wrapper would work with any libGL
conforming to the libGL ABI. Surely the stub generation can be automated
at least to some degree, maybe the Mesa glapi scripts can be (ab)used
for that.


-- 
Earthling Michel Dänzer   |http://www.vmware.com
Libre software enthusiast |  Debian, X and DRI developer



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#597019: libgl1-mesa-dev: missing static library (libGL.a)

2010-09-16 Thread Chris King
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 the libGL linked
 statically, whereas a dlopen based wrapper would work with any libGL
 conforming to the libGL ABI. Surely the stub generation can be automated
 at least to some degree, maybe the Mesa glapi scripts can be (ab)used
 for that.

Yes, I did end up writing a stub generator, since I was planning to
for the final project anyway.  Having the static library would simply
have been more convenient for development  testing.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#597019: libgl1-mesa-dev: missing static library (libGL.a)

2010-09-16 Thread Michel Dänzer
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 libGL?

Exactly.


  The downside is that the wrapper becomes specific to the libGL linked
  statically, whereas a dlopen based wrapper would work with any libGL
  conforming to the libGL ABI. Surely the stub generation can be automated
  at least to some degree, maybe the Mesa glapi scripts can be (ab)used
  for that.
 
 Yes, I did end up writing a stub generator, since I was planning to
 for the final project anyway.  Having the static library would simply
 have been more convenient for development  testing.

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
I don't know how offhand.


-- 
Earthling Michel Dänzer   |http://www.vmware.com
Libre software enthusiast |  Debian, X and DRI developer



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#597019: libgl1-mesa-dev: missing static library (libGL.a)

2010-09-16 Thread Chris King
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 libGL, but
 I don't know how offhand.

I thought so too, but haven't been able to find a way yet.  I think it
would require tricking ld.so into loading both copies of libGL.so.1,
which it seems reluctant to do.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#597019: libgl1-mesa-dev: missing static library (libGL.a)

2010-09-15 Thread Chris King
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/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32 (PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libgl1-mesa-dev depends on:
ii  libc6-dev 2.11.2-2   Embedded GNU C Library: Developmen
ii  libgl1-mesa-glx   7.7.1-2A free implementation of the OpenG
ii  mesa-common-dev   7.7.1-2Developer documentation for Mesa

libgl1-mesa-dev recommends no packages.

libgl1-mesa-dev suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org