-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
failure to link with pipewire-jack-audio-connection-kit-devel #142
Comments
Switching to JACK with:
then building jackctl works. After jackctl is built, the executable continues to work after reinstalling PipeWire's JACK implementation:
|
Be-ing
changed the title
downstream project fails to link with pipewire-jack-audio-connection-kit-devel
failure to link with pipewire-jack-audio-connection-kit-devel
Jul 29, 2021
The pkg_config crate may help. |
Building this crate by itself works. The failure only occurs when a downstream project tries to link. |
ssssam
added a commit
to ssssam/boucle
that referenced
this issue
Nov 16, 2021
CPAL cannot be used on Organelle. * Using default audio device gives a EPIPE error in snd_pcm_start() * Specifying device `default=CARD=Codec` fails because of RustAudio/cpal#615 * Using JACK backend fails for reasons I didn't investigate - the `feedback` example fails with 'unsupported configuration' even though it's clearly using a supported configuration. JACK is available on Organelle and can play sound, we just need to start it in the run.sh script. I don't have time to fix any of the CPAL problems so let's switch to JACK for everything. This can also be tested locally on desktop, but see: RustAudio/rust-jack#142
ssssam
added a commit
to ssssam/boucle
that referenced
this issue
Nov 21, 2021
CPAL cannot be used on Organelle. * Using default audio device gives a EPIPE error in snd_pcm_start() * Specifying device `default=CARD=Codec` fails because of RustAudio/cpal#615 * Using JACK backend fails for reasons I didn't investigate - the `feedback` example fails with 'unsupported configuration' even though it's clearly using a supported configuration. JACK is available on Organelle and can play sound, we just need to start it in the run.sh script. I don't have time to fix any of the CPAL problems so let's switch to JACK for everything. This can also be tested locally on desktop, but see: RustAudio/rust-jack#142
Be-ing
added a commit
to Be-ing/rust-jack
that referenced
this issue
Nov 30, 2021
This fixes linking with PipeWire's JACK headers. Fixes RustAudio#142
Be-ing
added a commit
to Be-ing/rust-jack
that referenced
this issue
Nov 30, 2021
This fixes linking with PipeWire's JACK headers. Fixes RustAudio#142
Be-ing
added a commit
to Be-ing/rust-jack
that referenced
this issue
Nov 30, 2021
This fixes linking with PipeWire's JACK headers. Fixes RustAudio#142
Be-ing
added a commit
to Be-ing/rust-jack
that referenced
this issue
Dec 1, 2021
This fixes linking with PipeWire's JACK headers. Fixes RustAudio#142
wmedrano
pushed a commit
that referenced
this issue
Dec 13, 2021
* jack-sys: search for jack library with pkg-config This fixes linking with PipeWire's JACK headers. Fixes #142 * jack-sys: add package.links=jack to Cargo.toml
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Trying to build jackctl which uses this crate when I had the pipewire-jack-audio-connection-kit-devel package for PipeWire's reimplementation of JACK installed on Fedora 34 failed with:
jackctl has no build.rs and I hope that can be avoided by fixing this upstream.
I ran into a similar issue building a C library that depends on JACK. The solution was to search for libjack in the path specified by pkgconfig rather than simply looking for libjack in the default library search path. The pipewire-jack-audio-connection-kit-devel package comes with a file /usr/lib64/pkgconfig/jack.pc which points to the location for the library:
The text was updated successfully, but these errors were encountered: