Re: Versioned symbols for 3.0?



On Tue, May 18, 2010 at 5:33 PM, Johannes Schmid <jhs jsschmid de> wrote:
> Hi!
>
>> The ultimate goal is being able to automatically detect at link time
>> that program A requires library B implementing at least version X of
>> the interface and embedding such information in packages
>> automatically. Just like we do for glibc with its GLIBC_x_y
>> interfaces.
>>
>> The changes required for glibc was:
>> 1) removing the -export-symbols-regex "^g.*" passed to libtool
>> 2) adding -Wl,-version-script=libglib-2.0.ver to libglib_2_0_la_LDFLAGS
>> 3) creating the .ver file
>>
>> A sample file (marking just one symbol as GLIB_2_24 for demonstration
>> purposes) looks like that:
> Are you talking about glibc or glib? It's a bit confusing to me...

glibc already provides versioning info for its symbols. I used
glib-2.0 as an example but I'd love to see these in all the platform
libs as they tend to have long cycles of ABI compatibility while
introducing new symbols with each version.

-- 
Patryk Zawadzki


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]