mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #275] Librespot Binaries #185
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#185
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @3l0w on GitHub (Dec 2, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/275
For guy who don't want to build the source, they can use this: https://github.com/gwilherm55/librespot_binaries
@ashthespy commented on GitHub (Dec 2, 2018):
Your link is broken - points to
https://github.com/gwilherm55/librespot_binariesl@3l0w commented on GitHub (Dec 2, 2018):
Thank you,Thank you, it's now fix
@kingosticks commented on GitHub (Dec 2, 2018):
You should probably specify which backends are compiled and and the fact that you don't have the raspberry pi 1/zero build.
@3l0w commented on GitHub (Dec 2, 2018):
arm-unknown-linux-gnueabiits pi 1?@kingosticks commented on GitHub (Dec 2, 2018):
Nope. https://github.com/librespot-org/librespot/blob/master/contrib/docker-build-pi-armv6hf.sh
@3l0w commented on GitHub (Dec 2, 2018):
I run this to have all the binaries :
docker run -v /tmp/librespot-build:/build librespot-cross@3l0w commented on GitHub (Dec 2, 2018):
When i use :
cargo build --release --target arm-unknown-linux-gnueabihf --no-default-features --features "alsa-backend" --verboseI got a error :
error[E0463]: can't find crate forstd| = note: thearm-unknown-linux-gnueabihf` target may not be installederror: aborting due to previous error
For more information about this error, try
rustc --explain E0463.error: Could not compile
libc.Caused by:
process didn't exit successfully:
rustc --crate-name libc /root/.cargo/registry/src/github.com-1ecc6299db9ec823/libc-0.2.40/src/lib.rs --color always --crate-type lib --emit=dep-info,link -C opt-level=3 --cfg 'feature="default"' --cfg 'feature="use_std"' -C metadata=dff7834e8e33583f -C extra-filename=-dff7834e8e33583f --out-dir /root/librespot/target/arm-unknown-linux-gnueabihf/release/deps --target arm-unknown-linux-gnueabihf -L dependency=/root/librespot/target/arm-unknown-linux-gnueabihf/release/deps -L dependency=/root/librespot/target/release/deps --cap-lints allow(exit code: 1)`
@kingosticks commented on GitHub (Dec 2, 2018):
Yeh sure, I can see what you've done but I'm just saying that isn't all the binaries. If you also want to provide the single armhf binary that works on all raspberry pi models then you must also run the other docker image. If you look you'll see it's different.
If you don't, that's fine of course, but you should make it clear as it will confuse some people. And then perhaps instead point to whatever that debian packaged thing is called. Raspot? Raspotify?!
@3l0w commented on GitHub (Dec 2, 2018):
I updated the README
@kingosticks commented on GitHub (Dec 2, 2018):
Have you tried that 2nd binary on a raspbery pi 1?
I'm not doing a very good job of explaining this. I think it's pretty clear the current wiki doesn't either.
@sashahilton00 commented on GitHub (Dec 2, 2018):
We'll start doing builds properly at some point, likely once we start versioning things properly and publish to crates.io. There are still a few things which we need to fix before I think we're ready to publish, those being handling reconnections, gapless, and daily mixes. The other issues can be fixed in later versions, as they're not game changing.
@3l0w commented on GitHub (Dec 2, 2018):
I dont know how i can build the 2nd binary on raspberry pi 1
@3l0w commented on GitHub (Dec 2, 2018):
If you need to change something in my repository make a pull request
@kingosticks commented on GitHub (Dec 2, 2018):
I think this can be closed unless we need an example to remind why the wiki needs updating.