I am using deluge compiled from source on debian and I am confused.
1. If I have libtorrent rasterbar installed from package and compile deluge it finds the .15 version of libtorrent and works
2. if I remove all both the libtorrent rasterbar .15 package and the python package
- run the build /install on libtorrent rasterbar .16 from source
- run the build and install on the created setup python
- then compile and install deluge, deluge defaults to its own OLD .14 copy of libtorrent.
What am I missing? what should I be looking for? do I need to move around some files after compile that make install does not take care of?
how to build libtorrent rasterbar from source?
Re: how to use libtorrent rasterbar from source?
Are you building the python libtorrent bindings? http://www.rasterbar.com/products/libto ... nding.html
The build script for Deluge will attempt to look for libtorrent and if it cannot find it, it will build and install its own version (defaults to 0.14).
The build script for Deluge will attempt to look for libtorrent and if it cannot find it, it will build and install its own version (defaults to 0.14).
Re: how to use libtorrent rasterbar from source?
Yes, I am building the bindings but it doesn't seem to find them... I must be missing something simple... I am not seeing any errors.
I really want to update as I seem to be having a hard time seeding to uTorrent users... I have noticed they connect and then disconnect rapidly and I suspect it is due to the lack of uTP ether due to preference or something users are setting.
I really want to update as I seem to be having a hard time seeding to uTorrent users... I have noticed they connect and then disconnect rapidly and I suspect it is due to the lack of uTP ether due to preference or something users are setting.
Re: how to use libtorrent rasterbar from source?
Just thought I would run through the steps that I have been using to build recently on ubuntu:
This will install libtorrent and bindings in correct place. I have substituted make install for checkinstall because checkinstall creates a deb package that then can be used by dpkg to remove all the installed files easily.
Also if using a tarball from svn so you would need to create the configure script by runnning the autotool script:
I have not mentioned dependencies however both running autotool.sh and configure will warn if missing. If updating from an already included libtorrent you can get the dependencies using apt-get:
Code: Select all
./configure --enable-python-binding
make
sudo checkinstall
Also if using a tarball from svn so you would need to create the configure script by runnning the autotool script:
Code: Select all
./autotool.sh
Code: Select all
sudo apt-get build-dep libtorrent-rasterbar