Ralf Wildenhues asked:
> Are we committing to a stable API and ABI now?
No, it's still the responsibility of the distributor of a shared library
package to ensure that its API is maintained (if the library uses libtool
versioning).
For restricting the exported symbols, there's
- the approach wi
* Paolo Bonzini wrote on Mon, Apr 06, 2009 at 07:34:35AM CEST:
> Ralf Wildenhues wrote:
> > * Bruno Haible wrote on Sun, Apr 05, 2009 at 10:42:45PM CEST:
> >> This patch makes it easier to distribute a library that was built by
> >> Makefile rules generated by Makefile.am.
> >
> > Are we committin
Ralf Wildenhues wrote:
> Hi Bruno, all,
>
> * Bruno Haible wrote on Sun, Apr 05, 2009 at 10:42:45PM CEST:
>> This patch makes it easier to distribute a library that was built by
>> Makefile rules generated by Makefile.am.
>
> Are we committing to a stable API and ABI now?
I think this is for Bru
Hi Bruno, all,
* Bruno Haible wrote on Sun, Apr 05, 2009 at 10:42:45PM CEST:
> This patch makes it easier to distribute a library that was built by
> Makefile rules generated by Makefile.am.
Are we committing to a stable API and ABI now?
Cheers,
Ralf
This patch makes it easier to distribute a library that was built by
Makefile rules generated by Makefile.am. Previously you had to write
lib_LTLIBRARIES = libgnurepacked.la
libgnurepacked_la_LIBADD = libgnu.la
Now you can write directly
lib_LTLIBRARIES = libgnu.la
Bruno
2009-04-05 Bruno Hai
