c0re100 / qBittorrent-Enhanced-Edition

[Unofficial] qBittorrent Enhanced, based on qBittorrent
https://github.com/c0re100/qBittorrent-Enhanced-Edition
Other
17.61k stars 1.21k forks source link

libtorrent 2.0 #482

Open PhilCity opened 1 year ago

PhilCity commented 1 year ago

Suggestion

Will libtorrent 2.0 be used?

Use case

No response

Extra info/examples/attachments

No response

abcfy2 commented 1 year ago

https://github.com/qbittorrent/qBittorrent/issues/18983

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.

b4bass commented 10 months ago

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

abcfy2 commented 10 months ago

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 https://github.com/c0re100/qBittorrent-Enhanced-Edition/issues/465#issuecomment-1474852136

You may modify

https://github.com/c0re100/qBittorrent-Enhanced-Edition/blob/v4_5_x/.github/workflows/cross_build.sh#L15

https://github.com/c0re100/qBittorrent-Enhanced-Edition/blob/416904b363014e3a30d908f39721243577e6ed64/.github/workflows/cross_build.sh#L15

Set LIBTORRENT_BRANCH to RC_2_0. Then use docker to build:

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 .github/workflows/

b4bass commented 10 months ago

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 seems to be the case with the Debian ones from OBS as well

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?

abcfy2 commented 10 months ago

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 seems to be the case with the Debian ones from OBS as well

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?

-nox uses static comiple, it static linked all the dependencies, and it does not use any system shared libraries. So you may always download from https://github.com/c0re100/qBittorrent-Enhanced-Edition/releases/latest/download/qbittorrent-enhanced-nox_aarch64-linux-musl_static.zip. This URL always point to the latest release. See: https://docs.github.com/en/repositories/releasing-projects-on-github/linking-to-releases#linking-to-the-latest-release

And I'll consider to switch to libtorrent 2.0 when upstream uses this version by default.