Please read the boost getting started manual
http://www.boost.org/more/getting_started/windows.html

You will have to run some command like

bjam --build-dir=C:/Temp/boost-build --toolset=gcc stage

where / is backslash, just that Joomla does not let me type backslash.

Update: OpenSSL is now required (due to some bad DLL dependencies, I do not advice you to use the prebuilt package). You need to compile it and copy the headers and libs to proper locations. Rename libeay32.a to libssleay32MT.a for now (I will fix this some day).

Also, boost 1.34 needs to be patched for mingw, see http://lists.boost.org/Archives/boost/2007/06/124040.php (luckily, you do not need to recompile boost after the patch).

All in all, compiling PokerTH on Windows is just not as easy as it should be, I'm afraid, due to all these dependencies...

Hello Lotodore,

how can I compile Qt with MinGW? I downloaded this file http://ftp.iasi.roedu.net/mirrors/ftp.trolltech.com/qt/source/qt-win-opensource-src-4.3.1.zip ,unpacked it to C:/QT/4.3.1 and changed into directory. There is a configure.exe, but what next?

Hi BuzzDee

The code below is untested adapted from linux:

Code:

configure.exe -static -qt-libpng -qt-zlib -qt-libjpeg -qt-gif -no-libtiff -no-libmng -no-qt3support -no-sql-sqlite -no-qdbus make sub-tools-all-ordered make sub-tools-install_subtargets-ordered make install_mkspecs make install_qmake

May be can try it this way.

Last night I tried to compile PokerTH under Windows. At 2:30 AM I gave up... No chance, too much trouble ... Perhaps you could release some nightly snapshot-version from cvs?

Greets,

Markus

What I am planning to do at some time is to provide a cmd script which downloads all the stuff needed, and builds everything on Windows. But currently I have very few time so I'm afraid this has to wait, sorry. I know that compiling PokerTH on Windows is not funny.

I don't like these nightly builds because I think the binary releases should be compatible to the current internet server, and if there are svn builds around this will be one big mess. Also, regularily updating them would be quite some work.

Using the svn version is really for "your own" because svn versions might not be compatible to the current public server. They might even be broken somehow.