Tribler

We make use of submodules, so remember using the --recursive argument when cloning this repo.

Dependencies

Debian/Ubuntu/Mint

sudo apt-get install scons build-essential libevent-dev python-libtorrent python-apsw python-wxgtk2.8 python-netifaces python-m2crypto vlc

Windows

TODO

OSX

TODO

Running Tribler from this repository

Unix

First clone the repository:

git clone --recursive  [email protected]:Tribler/tribler.git

or, if you don't have added your ssh key to your github account:

git clone --recursive  https://github.com/Tribler/tribler.git

Then build swift and copy the binary where Tribler expects it to be:

cd  tribler/Tribler/SwiftEngine
scons #or scons -j8 if you have 8 cores on your machine.
cp swift ../..
cd ../..

Done! Now you can run tribler by executing the tribler.sh script on the root of the tree:

./tribler.sh

Windows

TODO

Submodule notes

• As updated submodules are in detached head state, remember to check out a branch before commiting changes on them.
• If you forgot to check out a branch before doing a commit, you should get a warning telling you about it. To get the commit to a branch just check out the branch and do a git cherry-pick of the commit.
• Take care of not accidentally commiting a submodule change with git commit -a
• Do not commit a submodule update without running all the tests first and making sure the new code is not breaking Tribler.

Branching notes

• The branches starting with svn_ are there for historical reasons, they will eventually be tagged and removed. Do not fork them or commit stuff to them. They should be considered read-only.
• The master branch will contain the latest released code (starting from release 6.1.x, the first release after moving to GitHub)
• The devel branch contains the unreleased code which will make it into the next release.