On 16:11 Mon 15 Nov , Dan Nicholson wrote: > On Mon, Nov 15, 2010 at 10:38 AM, Julien Cristau <[email protected]> wrote: > > On Mon, Nov 15, 2010 at 13:28:34 -0500, Gaetan Nadon wrote: > > > >> On Mon, 2010-11-15 at 15:35 +0100, Julien Cristau wrote: > >> > >> > If you want to install it as a shared library you also want to > >> > track its ABI and give it a SONAME, which is more work. Shipping > >> > it as a PIC static lib which you don't have to be as careful with > >> > possible ABI breaks, but you can still embed it in something like > >> > a python module (which must be PIC). > >> > > >> > >> This is an important point. We are waisting time trying to guess > >> what this patch is for. > >> > > Oh, I know what it's for, it's needed for pyxf86config. I just > > don't think anyone is prepared to commit to a stable ABI for > > libxf86config, so installing it as a shared library may not be the > > best plan.
IIRC, installing a shared lib with a SOVER of 0 means no promise of ABI stability... I'd rather see it done in a "right" way than hacking around the same issue and ending up with bundled static libs in places where you wouldn't expect them. -- Thanks, Donnie Donnie Berkholz Sr. Developer, Gentoo Linux Blog: http://dberkholz.wordpress.com
pgp8FAId1c5ip.pgp
Description: PGP signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
