Re: packaging shared libraries without autoconf and automake

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

 



Once upon a time, Eric Smith <eric@xxxxxxxxxxxx> said:
> I don't want to replace the upstream Makefile with use of autoconf and 
> automake, and the libtool documentation doesn't really explain how to 
> use libtool without those.  Can I just do the shared library versioning 
> "by hand", by creating the appropriate symlinks in the package?  Or is 
> there some other preferred way to deal with this kind of situation?

If upstream isn't building a shared library, then you have no good way
to set a version and then maintain an ABI.  If other software that links
against the library is only expecting a static, they won't expect to
have to deal with ABI changes either.

No matter how you make a shared library, I'd suggest getting that change
accepted upstream before trying to put it in Fedora.
-- 
Chris Adams <cmadams@xxxxxxxxxx>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux