-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
libtorrent 2.0 #482
Comments
It seems libtorrent 2.0 has some performance issues. So upstream still use libtorrent 1.2 for release building. But it's fine you can use libtorrent 2.0 for building yourself. |
Using ubuntu 22.04 ppa, it seems to be using libtorrent-rasterbar20 (Libtorrent: 2.0.9.0) like the official one Is there a way to use the libtorrent-rasterbar10 using nox ? Because I cant use the AppImage headless |
See #465 (comment) You may modify
Set docker run --rm -v `git rev-parse --show-toplevel`:/build abcfy2/muslcc-toolchain-ubuntu:x86_64-linux-musl /build/.github/workflows/cross_build.sh Then the build artifacts should under |
Hi, sorry I didn't open a new issue, but I'm actually trying to use the 1.2 version as opposite to the 2.0 one shipped with the Ubuntu ppa. It could be nice if there was a way to use the 1.2 nix version as a package (jammy) so I can get auto update. Also I'm using aarch64 on a pi 4 If I can't use a repo, how do I use qbittorrent-enhanced-nox_aarch64-linux-musl_static.zip the 1.2 lib and keep all dependencies in sync? |
And I'll consider to switch to libtorrent 2.0 when upstream uses this version by default. |
Suggestion
Will libtorrent 2.0 be used?
Use case
No response
Extra info/examples/attachments
No response
The text was updated successfully, but these errors were encountered: