To compile yourself:

1. Download Qt development kit (choose "Go LGPL", then click on "Qt SDK for Windows") and install in a directory of your choice (default: C:\2010.xx.x , where 2010.xx.x is the version of your Qt installation) ; MinGW will be installed in Qt directory automatically
2. Add some paths to your environment variables: <QtDir>\bin;<QtDir>\qt\bin;<QtDir>\mingw\bin (<QtDir> means the directory where Qt is installed, usually C:\2010.xx.x)
3. Download and install Git for Windows
4. Download the pre-compiled dependencies and extract them into the MinGW-root created by Qt-Installation
5. Get the current sources (from git)
6. run qmake -r in main directory (will build the debug configuration which is faster to build, but uses big dll files; use qmake -r CONFIG+=release for the release configuration)
7. run 'make' at the same location

Alternatively to running qmake -r and make manually, you might also want to build the project using Qt Creator by Qt Software. To do that, open the file himd.pro located in the root directory of the source tree. If you want to run the GUI QHiMDTransfer tool, make sure to choose the run configuration qhimdtransfer instead of himdtest. The latter will just exit with an error code if no command line parameters are provided.

To test QHiMDTransfer:

Download and install QHiMDTransfer windows self installer. Updated EXE file (now with recorder autodetection!) at zipped QHiMDTransfer.exe, will be merged to the installer soon.

Download everything and extract into your mingw root. It is <QtDir>\mingw (<QtDir> means the directory where Qt is installed, usually C:\2010.xx.x). To run QHiMDTransfer, you just need the files from the runtime column. To compile QHiMDTransfer, you also need the development stuff. MinGW automatically gets installed if you install the Qt development kit for Windows.

* Note: you need the zlib development files only for recompiling taglib, not for recompiling QHiMDTransfer

This stuff is not needed. It produces just the zip files linked above. The instructions shown should work on debian Linux.

Perform the following steps.

1. Get libmad-0.15.1b.tar.gz, local copy at libmad-0.15.1b.tar.gz for GPL reasons (I am distributing a binary)
2. Get libmad.patch
3. In the directory both files were saved to, enter:

tar -xvzf libmad-0.15.1b.tar.gz
patch -p0 < libmad.patch
cd libmad-0.15.1b
autoconf
touch -d '1/1/1970' configure.ac
./configure --host=i586-mingw32msvc --prefix=/ --disable-static
make
make DESTDIR=`pwd`/tmp install
cd tmp
i586-mingw32msvc-strip bin/libmad-0.dll
mkdir manifest
echo bin/libmad-0.dll manifest/libmad-runtime.mft > manifest/libmad-runtime.mft
echo lib/libmad.* include/mad.h manifest/libmad-devel.mft > manifest/libmad-devel.mft
zip ../../libmad-runtime.zip bin/libmad-0.dll manifest/libmad-runtime.mft
zip ../../libmad-devel.zip lib/libmad.* include/mad.h manifest/libmad-devel.mft

Perform the following steps.

1. Get libmcrypt-2.5.8.tar.bz2 via Sourceforge Download system, local copy at libmcrypt-2.5.8.tar.bz2 for GPL reasons (I am distributing a binary)
2. Get libmcrypt.patch
3. In the directory both files were saved to, enter:

tar -xvjf libmcrypt-2.5.8.tar.bz2
patch -p0 < libmcrypt.patch
cd libmcrypt-2.5.8
autoconf
touch -d '1/1/1970' configure.in
./configure --host=i586-mingw32msvc --prefix=/ --disable-static
make
make DESTDIR=`pwd`/tmp install
cd tmp
i586-mingw32msvc-strip bin/libmcrypt-4.dll 
mkdir manifest
echo bin/libmcrypt-4.dll  manifest/libmcrypt-runtime.mft | tr ' ' '\n' > manifest/libmcrypt-runtime.mft
echo bin/libmcrypt-config include/mcrypt.h include/mutils/mcrypt.h lib/libmcrypt* share/aclocal/libmcrypt.m4 share/man/man3/* manifest/libmcrypt-devel.mft | tr ' ' '\n' > manifest/libmcrypt-devel.mft
zip ../../libmcrypt-devel.zip -@ < manifest/libmcrypt-devel.mft
zip ../../libmcrypt-runtime.zip -@ < manifest/libmcrypt-runtime.mft

Perform the following steps. It will build a static (minimal) sox library. mad support is disabled, as it won't link with a dynamic mad library because limitations of the Windows executable file format that would need an annotation in the mad include file (so it is essentially a bug in our mad build). As sox is only used to write wave files, disabling mad is no problem.

1. Get sox-14.2.0.tar.gz via Sourceforge Download system, local copy at sox-14.2.0.tar.gz for GPL reasons (I am distributing a binary)
2. In the directory both files were saved to, enter:

tar -xvzf sox-14.2.0.tar.gz
cd sox-14.2.0
./configure --host=i586-mingw32msvc --prefix=/ --disable-symlinks --without-mad
make
make DESTDIR=`pwd`/tmp install
cd tmp
i586-mingw32msvc-strip --strip-unneeded lib/libsox.a
mkdir manifest
find lib -type f > manifest/sox-devel.mft
echo include/* manifest/sox-devel.mft | tr ' ' '\n' >> manifest/sox-devel.mft
zip ../../sox-devel.zip -@ < manifest/sox-devel.mft

This has been done manually, so there is no ready-made script for it.

1. Get the zlib development files (linked above) and put them into your MinGW path.
2. Get taglib-1.6.3.tar.gz, local copy at taglib-1.6.3.tar.gz for GPL reasons (I am distributing a binary)
3. Apply this patch to the CMakeLists.txt to help cmake find zlib: taglib-cmake.diff
4. run cmake -G "MinGW Makefiles" to create the Makefiles
5. run mingw32-make to build libtag
6. run mingw32-make install to install (default destination: %Program Files%\taglib)
7. run strip on libtag.dll to reduce the size by removing debugging symbols
8. put libtag.dll into a zip file to obtain the "runtime" zip file linked above.
9. We don't need the C bindings, so you can remove lib\taglib_c.dll.a, lib\pkgconfig\taglib_c.pc, include\tag_c.h
10. Add the missing pkg-config file from taglib.pc into lib\pkgconfig
11. pack the contents of include and lib to get taglib-devel.zip