Closed micmac1 closed 3 years ago
it definitely will not build against the older version. We should have some packaging fixes in for raspian probably tomorrow to set up the old and new versions of spandsp installing side by side so you can use the new version. Wheels are in motion on an official spandsp 2.0 release as well, which will roughly be based on this code.
it definitely will not build against the older version. We should have some packaging fixes in for raspian probably tomorrow to set up the old and new versions of spandsp installing side by side so you can use the new version. Wheels are in motion on an official spandsp 2.0 release as well, which will roughly be based on this code.
Can I take away from this that this spandsp is not ABI/API compatible with the original 0.0.6 and applications that are not FreeSWITCH would need changes to be able to use it (it being 1.99)?
Correct, this is a major version upgrade that is about to be released of spendsp with major api/abi changes. We are working on doing proper packages that can be along side. Note that this is not a fork, and is maintained by the author of spandsp.
see the commits that just went in on versioning/deb packaging. I think this gets us closer to what you need
Thanks Mike!
Hi all,
I maintain the FreeSWITCH package for OpenWrt and the FreeSWITCH update 1.10.4 causes me some consternation regarding the spandsp dependency.
I saw that there was a commit made shortly before the release that lowered the spandsp version requirement from 1.99 to 0.0.6, apparently to be able to compile against the spandsp version used in Debian. But I have to wonder if this would really work (on Debian), because OpenWrt uses the same spandsp version 0.0.6 and the few patches that Debian adds on top don't seem to be related to the build failure I see when trying to compile FreeSWITCH against the OpenWrt spandsp 0.0.6 (I'll paste the log below in case anybody is curious).
So for all I know spandsp 0.0.6 is not compatible with FreeSWITCH 1.10.4 and one needs this spandsp fork (1.99).
Which leads me to the part which gives me consternation :)
I cannot compile FreeSWITCH without spandsp, because libfreeswitch.so seems to have a hard dependency on it (on version 1.99, because as mentioned building against 0.0.6 fails). But the fork uses the same library name as the "original" version 0.0.6. So I'd like to know your view on how things should go from here. Do you consider this fork with version 1.99 to be a "drop-in" replacement for the "original" version 0.0.6? Is 1.99 ABI/API compatible with 0.0.6? The SONAME is the same, which suggests that it should be ABI/API compatible?
In OpenWrt we have not only FreeSWITCH that depends on spandsp. We also package Asterisk, yate, rtpengine and baresip and they all have dependencies on spandsp. Will they work without changes with this fork of spandsp, with spandsp 1.99?
If this is not the case I will probably put some efforts into trying to rename the library of this fork to something different, so that the "original" spandsp can coexist with this "fork", in order for the other applications that depend on spandsp to keep working as expected.
I would really appreciate your feedback on this matter.
Thanks and kind regards, Seb