Source for BiglyBT, a feature filled, open source, ad-free, bittorrent client. BiglyBT is forked from Vuze/Azureus and is being maintained by two of the original developers as well as members of the community. With over 15 years of development, there's a good chance we have the features you are looking for, as well as the decade old bugs you aren't looking for :)
Method | Address |
---|---|
PayPal | BiglyBT's Donation Page |
BCH/BTC/BSG/BSV | 1BiGLYBT38ttJhvZkjGc5mCw5uKoRHcUmr |
DASH | XjDwmSrDPQBaLzCkuRHZaFzHf7mTVxkW9K |
DOGE | DMXWdEtPUJc5p2sbHGo77SvqFXKTR8Vff1 |
ETH/ETC | 0x4e609B5EF88C8aA8Ab73945fD1ba68c9E27faC75 |
LTC | LKGc2utCrGfojpYsX3naT9n1AxjLiZ5MMG |
TRX/BTT | TAbsb7pjEEWNpXFvPf49rfVhFSB2e3dAM7 |
XRP | rPFKfbx2tuzMMaz7Zy99M6CquHKgp9srSb |
Getting the basics to compile from source is pretty straightforward:
core/src
and uis/src
as project roots (source modules)core/lib/*
and one of the swt.jars at /uis/lib/
:swt-win64.jar
on Windowsswt-cocoa-64.jar
on OSXswt-linux-64.jar
on Linux (GTK)core/lib/*
uis
module depend on core
. Core
should not depend on uis
IntelliJ IDEA will do all these steps for you with its wizard.
If you wish IntelliJ IDEA to show MessageBundle strings instead of keys, as well as reduce the number of NPE warnings, you can attach the external annotations either by:
<module>/<module>.iml
add to component:
<annotation-paths>
<root url="file://$MODULE_DIR$/../external-annotations" />
</annotation-paths>
External Annotations definitions are a WIP and not complete list of definitions.
Running is only few more steps:
com.biglybt.ui.Main
in module uis
Working Directory should be a new folder, since the app will write things to it. Put the aereg.dll
or libOSXAccess.jnilib
in there.
When a normal user is running the app, the working directory is where the jar, executable, and libraries (dll, so, jnilib) are.
-Dazureus.config.path=<some config path>
We build our installers using Install4j, multi-platform installer builder