Conversation
|
Thanks, I'll take a look at this. It's really cool you put this together. My plan (and existing WIP) goes in a different direction, binding quiet from inside a C python extension. That's probably going to take a while to finish and isn't particularly high priority though. I'll see about how to provide this in the interim. Regarding ARM, those missing symbols aren't used by liquid directly. I seem to remember they're specific to libfec. Did you happen to link liquid against fec and then drop in correct+shim? That may not build the correct linkage. Edit: to clarify, I suspect compiling against fec may be the issue. I think it has some extern symbols in use in its header file. Compiling against correct will fix this. |
|
Oh, the libcorrect works on ARM, I forgot to remove the header file |
|
any updates on this issue? I would like to implement quiet in some python projects and this would help a lot |
@brian-armstrong
This is an attempt to build a ctypes binding for libquiet. Hope it helps.
Changes
scripts/libs.shquiet/quiet.py- ctypes binding for libquiet.sosetup.pyUsage
See examples
decode()andtest()ofquiet/quiet.pyknown issues
if portaudio lib is in system lib path, libquiet will use it, which cause link error. A quick fix is to remove
portaudio-devlibrarynot work on ARM (raspberry pi). It seems libcorrect is not a complete replacement for libfec. The error message is: