Registered Member
|
Now that 3.0 is built with qt 4, ive heard that windows support would be considered at this time, is there any news about adding it?
|
Moderator
|
|
Registered Member
|
What would be required to make a windows port? Now that kTorrent is using qt 4, should someone just have to recompile it on windows for it to work?
I for one think that if it does get a port that the popularity of ktorrent would skyrocket its much better than utorrent imho. |
Moderator
|
unfortunately it's not that easy, ktorrent uses unix socket that are not cross platforms, on windows it should use winsock that's like unix sock but it still need some changes, also ktorrent uses symlinks that doesn't exist on windows and the logrotate uses k3process that's not available on windows(but i think it could be disabled without any problems) and there could be other incompatibilities that I haven't found yet |
Registered Member
|
|
Moderator
|
|
Moderator
|
ah good i'm playing around with the code, there are a lot of unix only things but most of them are easy to port |
Registered Member
|
getting to work it under Vista may however turn out to be a completely different matter than getting it to run under any Win32 version regards, Segmented |
Registered Member
|
What exactly do you mean? We should get a thread set up that shows all of the steps that need to be taken for full windows computability and move forward from there. For instance as stated in this thread http://ktorrent.org/forum/viewtopic.php?t=2299 Weigh the pros and cons of Unix Sockets and a rewrite with Qt sockets(which imho are very improved since qt3). |
Moderator
|
They are still signal based, so they would not fit in at all in the current code. We use 2 different threads for networking, one for upload and one for download. These threads are used to make the spead limits work properly. With signal based stuff this proved to be much more difficult to get it working. We have used both Qt3 sockets and KDE3 sockets in earlier versions (1.X series). And we didn't get it right until we moved to the current architecture. It will be much easier to just throw in a couple of #ifdef WIN32 statements. |
Moderator
|
|
Registered Member
|
|
Moderator
|
|
Registered Member
|
|
Moderator
|
Registered users: Bing [Bot], Evergrowing, Google [Bot], rblackwell