-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to build on gnu/linux with portaudio jack backend #403
Comments
I had to apply the same patch on trisquel.info where jack was not installed at all |
Hey @CastixGitHub yep, thanks - that commit you reference was a quick fix (for #393 ) and it wasn't a principled "Extempore Jack is dead" thing. So since you've got a patch which adds it back I'll restore the build option ( Having said that, it's still true that neither @digego or I are using Jack, so it may well not work. If you find any issues, we'd happily apply any more patches. |
Thanks for submitting this issue. I just experienced the same problem. I'm not familiar with |
@eihli I'm not sure about you question, I'll try anyway t reply I see that the portaudio code have "a sort of adapter" (hostapi) between backends, the jack one is #include <jack/types.h>
#include <jack/jack.h> and I'm not a C programmer, I don't know from where these header files are found by the compiler and where are installed (not true, it's POSIX) now I mean, in my situation jack was found by cmake, and tried to build against it, and failed. I also tested extempore with pipewire's implementation of jack, that is also found by portaudio (here's proof https://github.com/PortAudio/portaudio/blob/2dc8b6eb17ac5fda1f89722cfa0889bfc6e73434/cmake/modules/FindJACK.cmake#L17) and it seems to work well (built with the patch above, I did't test without it) (tested with pw-jack, not the dropin replacement) (I'm not suggesting you to use pipewire) small resume of the current jack implementations: Happy to see your issue is also solved anyway |
@CastixGitHub @eihli thanks again for looking into the Jack stuff. I'm open to a PR which re-adds the Jack support (as long as it doesn't complicate the setup for other backends). @eihli adding One of the other tricks is adding "does Extempore support this audio backend" to the test suite. Extempore's test suite (which runs automatically in a GH action on push) has to run with the Anyway, I think what I'm suggesting is that if you do (a) find a nice way to add the Jack support back in (again, using the |
One other thing - unfortunately I'm in lockdown at the moment and only have my MBP with me (my linux machine is still at work, and not remotely accessible 😭 ). So I'm limited in my ability to test Jack stuff at the moment (although others will be able to test it - you could also ask for testing help on the mailing list). |
Hello again,
In commit 55b47d7
the compile option to disable jack support disappeared
anyway, I get a bunch of undefined references.
My installed version of jack is
jack2-1.9.18-1
with linux5.12.4
I would be happy to get jack support, but even disabling it is ok for me.
reporting here even if the bug seems upstream to make it known
I've done a patch for adding back the option in the aur package, feel free to merge it
The text was updated successfully, but these errors were encountered: