Deluge Forum

Hi, I compiled the latest libtorrent and openssl.
Just Copy the content in the program files\deluge folder

In my opinion it's better compile it yourself,
but I think people like things as-is

End of my support:
1/1/2020
See my post in this thread for info:

(updated 26/09/2019) (date european format)
https://www.mediafire.com/file/o43t2ecu ... s6.7z/file

(archive)
http://www.mediafire.com/file/fk7kssad3 ... s1.7z/file
https://www.mediafire.com/file/n04201no ... s2.7z/file
http://www.mediafire.com/file/bs8bt3qvh ... s3.7z/file
http://www.mediafire.com/file/ac435ftb6 ... s4.7z/file
http://www.mediafire.com/file/7b7kqpn4t ... s5.7z/file

yeah~~ works!

I have tried compile by myself... but in widows I always have so many errors...
How can you do that? Can you post your environments?

thanks,

some things were indeed complicated.

I'll try to make it comprehensive.

You need to compile openssl 1.0.2 openssl for deluge and openssl 1.1.1 for libtorrent
nasm
python 2.7
microsoft visual C compiler 2008 (link below)
https://www.microsoft.com/en-us/downloa ... x?id=44266
libtorrent 1.1.x
(libtorrent 2.x is unsupported with the compiler)
boost 1.65.1 (latest supported boost for compiler)
boost build from boost 1.68.0 (you can use the latest boost build for an older boost source, I will go into detail later)

1.compilation instructions
open MSVC2008 32-bit command prompt
check of environment doesn't list other compilers

for openssl 1.0.2 follow instructions deluge:
set PATH=C:\Users\IEUser\AppData\Local\nasm;%PATH%
perl Configure VC-WIN32 --prefix=C:\apps\OpenSSL-1.0.2q-VS2008-Win32\
ms\do_nasm
nmake -f ms\ntdll.mak
nmake -f ms\ntdll.mak test
open MSVC2008 32-bit command prompt in administrator mode
nmake -f ms\ntdll.mak install

for openssl 1.1.1 do:
perl Configure VC-WIN32 --prefix=C:\apps\OpenSSL-1.1.1a-VS2008-Win32
nmake
nmake test
open MSVC2008 32-bit command prompt in administrator mode
nmake install
copy and rename:

openssl-1.1.1a-VS2008-WIN32\lib
copy libcrypto.lib as crypto.lib
copy libssl.lib as ssl.lib

for libtorrent:
two versions of boost are needed:
extract boost 1.65.1
extract boost 1.68.0 (you can probably safely use te latest boost instead)
my next explanation is derived from this:
https://www.libtorrent.org/building.htm ... setup-bbv2
https://dev.deluge-torrent.org/wiki/Building/libtorrent

open MSVC2008 32-bit command prompt

edit: forgot vc9 command
run C:\apps\boost_1_68_0\tools\build\src\engine\build.bat vc9


set BOOST_BUILD_PATH=C:\apps\boost_1_68_0\tools\build\src\engine\bin.ntx86
set PATH=%BOOST_BUILD_PATH%;%PATH%
set BOOST_ROOT=c:\apps\boost_1_65_1
create the file user-config.jam in this directory with these lines:

using msvc : 9.0 : : <setup>"c:\\users\\%USER%\\AppData\\Local\\Programs\\Common\\Microsoft\\Visual C++ for Python\\9.0\\vcvarsall.bat" ;
using python : 2.7 ;

use boost-build to compile libtorrent:

EDIT: use b2 in the libtorrent\bindings\python map

b2 libtorrent-link=static boost-link=static release optimization=space encryption=on crypto=openssl include=C:\apps\OpenSSL-1.1.1a-VS2008-Win32\include linkflags=/LIBPATH:C:\apps\OpenSSL-1.1.1a-VS2008-Win32\lib address-model=32 toolset=msvc-9.0 --hash

I get a lot of text formatting problems but it compiles correctly

Thanks! Registered just to write this

No problem

I decided to continue with updates

Thanks for this, and the recent update!

Awesome, hope you'll continue updating.

Would it be possible that you could do one with libtorrent 1.2.1 ?

It's not possible.

libtorrent 1.2 needs a newer msvc compiler then deluge 1.3 uses.
deluge 2.0 will have support for libtorrent 1.2 included in the source code I think

When deluge 2.0 has an installer for windows it will be possible

What's wrong:
openssl for Deluge ends this year. (openssl 1.0.2)
So if you continue to use it know that next year there are no security patches for openssl 1.0.2 anymore

What to do:
It's recomended to use this build only until the end of year

Extra info:
Not that there can be other security issues in the future,
since deluge 1.x is old software,
it probably has a lot other security issues than openssl.
That's not to be alarming but a reminder.
it's pretty common for software and is very likely not exploited.

Happy holidays,

Nekotan