| Git Clone URL: | https://aur.archlinux.org/biglybt.git (read-only, click to copy) |
|---|---|
| Package Base: | biglybt |
| Description: | Feature-filled Bittorrent client based on the Azureus project |
| Upstream URL: | https://www.biglybt.com/ |
| Licenses: | GPL3 |
| Submitter: | Det |
| Maintainer: | mrxx |
| Last Packager: | mrxx |
| Votes: | 19 |
| Popularity: | 0.185813 |
| First Submitted: | 2017-12-26 15:31 (UTC) |
| Last Updated: | 2024-10-05 22:24 (UTC) |
centqwerG7890FCT, on my machines it starts like this:
Starting BiglyBT...
Suitable java version found [java = openjdk 14.0.1 2020-04-14]
Using swt/swt-x86_64.jar v4.924
Maybe you're using an incompatible java package.
Use "archlinux-java" to fix your java environment or select a different one (I've installed jre-openjdk).
Can't launch. I get the following errors: GUI could not be loaded. java.lang.UnsatisfiedLinkError: Could not find SWT library. Reasons: no swt-gtk-4934r5 in java.library.path [/opt/biglybt] no swt-gtk in java.library.path [/opt/biglybt] ~/.swtlib/linux/x86_64/libswt-gtk-4934r5.so Can't load library: ...
Thanks, eschwartz and SolarAquarion.
A fake homedir is created below $srcdir now and the installer writes everything into it.
Can't you trick the installer into writing those files into the $srcdir by faking the $HOME?
SolarAquarion, I've changed this back to the situation as it was when I adopted the package (where neither the app launcher link nor the link on the Desktop worked on the build machine because the .desktop files created by the program installer had a wrong execution path).
Now, on the build machine, the program installer again creates a link on the user's Desktop, and even worse, still with wrong Exec= content.
As proposed by you this link is no longer removed immediately, but a message in post-install directs the users to remove it on their own (and, just in case it reappears one day, also the link in .local/share/applications).
trick the installer into "HOME=$srcdir" or something like it
you should probably do an if for the " ~/.local/share/applications", because what if you build it in a chroot?
You should probably do a post_upgrade and post_install message instead of deleting stuff in the PKGBUILD or something that isn't in the build chroot
Added armv7h to archs.
Works fine on armv7h (Raspberry Pi), the PKGBUILD only lists x86_64. You need to create the ~/.local/share/applications if it doesn't exist or makepkg will fail.
If you want to use it headless on a PI but want to change the biglybt options using the GUI on your computer:
Set up X forwarding : https://wiki.archlinux.org/index.php/OpenSSH#X11_forwarding
SSH into the pi with -Y ; -X didn't work for me (ssh -Y 192.168.1.32)
Since SWT on arch linux arm is compiled for aarch64 and biglybt uses the x86_64 library, you need to either compile it for armv7 or find a compiled library, you can download one from https://rpmfind.net/linux/mageia/distrib/6/armv7hl/media/core/release/eclipse-swt-4.6.3-6.mga6.armv7hl.rpm ; extract the rpm and get the swt.jar file.
Move the swt.jar file to /opt/biglybt/swt/swt-unknown.jar (unknown because uname -p returns unknown for the pi, and biglybt uses uname -p to find the arch).
Install gtk and you can now run biglybt and the GUI will be forwarded.
Thank you, yochananmarqos. Added the suggested optional dependencies and set java-runtime to >=8.
Pinned Comments
mrxx commented on 2022-11-01 12:48 (UTC)
In order to get rid of annoying update messages at startup, go into Tools > Options > Interface > Start. Disable the 'Check for latest version" and 'Auto download updates' options.
Also disable 'Enable plugin update checking' in Tools > Options > Plugins > Plugin Update.