4.0 breaks the ABI....ergo the major version bump.
I see that Fedora does not mandate shared library usage
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_shared_libraries
Applications linking against libraries SHOULD link against shared libraries not
static versions.
So yes...it's preferable to use dynamic...when it works...and in this case it's
not the best solution for your users.In WSJT-X's case you'll be a lot better
off (and many more happy users) if you use the hamlib.tgz provided with WSJT-X.
de Mike W9MDB
On Thursday, March 26, 2020, 09:17:40 AM CDT, Christoph Berg
<[email protected]> wrote:
Thanks Bill.
Re: Bill Somerville 2020-03-26
<[email protected]>
> This is tricky area, even if there were many more Hamlib releases it is
> still hard to get the latest rig support.
If this discussion is only about rig support then I guess we can worry
a lot less. We could even backport the extra rigs from hamlib and put
it into the system lib.
The problem would be much bigger if wsjtx started to rely on actual
features ("symbols" in library speak) that aren't in the official
hamlib release, but that doesn't seem to be the case.
Christoph
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
