Tried building 64-bit qbt against it and failed.
I'd say a lot of problems come from libtorrent. Linking it is not possible against --layout=system boost builds. A lot of undocumented (for Windows) jam features like disk-stats=on fail completely.
Also libtorrent build cmd from qbt wiki:
Code: Select all
bjam -q --with-filesystem --with-thread --toolset=msvc variant=release link=static runtime-link=shared
From libtorrent Jamfile:
Code: Select all
feature timer : auto boost absolute performance clock system_time
: composite propagated link-incompatible ;
feature.compose <timer>boost : <define>TORRENT_USE_BOOST_DATE_TIME=1 ;
feature.compose <timer>absolute : <define>TORRENT_USE_ABSOLUTE_TIME=1 ;
feature.compose <timer>performance : <define>TORRENT_USE_PERFORMANCE_TIMER=1 ;
feature.compose <timer>clock : <define>TORRENT_USE_CLOCK_GETTIME=1 ;
feature.compose <timer>system_time : <define>TORRENT_USE_SYSTEM_TIME=1 ;
Will try to build 2.9.9 again.
About 64-bit stuff. There are some native x64 applications, e.g. 7zip, Opera, 3rd party firefox builds (PaleMoon), MPHC. And they all work fine.
64-bit comes with a bunch of registers, which compiler can use unlike i686.
Anyway, the biggest problem of Windows is that most of the stuff was written UNPORTABLE to a different arch/OS or uses i686 only obfuscators/protectors. Hence the lack of native 64-bit soft.
EDIT:
The error i'm getting: http://pastebin.com/ryvBeszS
Trying with DEFINES += BOOST_ASIO_SEPARATE_COMPILATION in winconf.pri
Getting this: http://pastebin.com/j0XeNkeN
Looks like the culprit is BOOST_NO_EXCEPTIONS in libtorrents torrent_handle.hpp. Will try to get around this.