Splitting up a library without breaking ABI?

2011-08-23 Thread Stef Walter
The libgcr library lives inside the gnome-keyring project. I'd like to split it out into its own module, which is easy enough. But at the same time I'd like to split it into two libraries: one with a GTK+ dependency (UI bits), and the other without. I'm not a release 'superstar', hence the

New release for ptlib/opal needed by ekiga

2011-08-23 Thread Eugen Dedu
Hi, A new release of ekiga, 3.3.2, is made right now. As usually :o(, it needs new ptlib and opal library releases, 2.10.2 respectively 3.10.2. I will upload them shortly. Please contact me for any question. Cheers, -- Eugen Dedu Ekiga maintainer

Re: Splitting up a library without breaking ABI?

2011-08-23 Thread Matthias Clasen
On Tue, Aug 23, 2011 at 4:20 AM, Stef Walter st...@collabora.co.uk wrote: Is there a way to split a library into two without breaking ABI? Not really, now. The current pkg-config file library is libgcr-3.so. Would it work to have libgcr-3.so depend on the two new libraries (eg:

Re: Splitting up a library without breaking ABI?

2011-08-23 Thread Josselin Mouette
Le mardi 23 août 2011 à 10:20 +0200, Stef Walter a écrit : Is there a way to split a library into two without breaking ABI? The current pkg-config file library is libgcr-3.so. Would it work to have libgcr-3.so depend on the two new libraries (eg: libgcr-base-3.so, libgcr-gtk-3.so). What I

Re: Splitting up a library without breaking ABI?

2011-08-23 Thread Daniel Macks
On Tue, 23 Aug 2011 19:35:46 +0200, Josselin Mouette wrote: Le mardi 23 août 2011 à 10:20 +0200, Stef Walter a écrit : Is there a way to split a library into two without breaking ABI? The current pkg-config file library is libgcr-3.so. Would it work to have libgcr-3.so depend on the two new