Branden Robinson ([EMAIL PROTECTED]):
> I'd like to solicit opinions, especially from the Core Team, about the
> shared vs. static extension library situation. Debian just went
> through a bit of pain and suffering as regards SDL in our development
> branch, partly because we have 12 architectures to supprt for our next
> release.
Sorry to add to the spam, but we were discussing this on IRC and
couldn't come up with an answer.
Why not just release shared libraries on the client-side? How is
library versioning insufficient to handle API changes? The current .a
situation is causing lots of problems.
Personally, I really don't like the idea of separate _pic.a versions.
As an aside, we have the same problem with libmpeg2.a. However in
this case, if you build libmpeg2 as PIC, then the performance drops by a
significant amount (roughly 5-15%) on x86, since the optimizer has lost
a register. This creates a huge problem for video plugins which use
libmpeg2. However, I don't think that this is the problem for the X
client libs..
--
Billy Biggs [EMAIL PROTECTED]
http://www.billybiggs.com/ [EMAIL PROTECTED]
PGP signature
