Hello Uwe,
Thanks for your replay.
I have started looking at VYM code and managed to build it on Windows after removing the dbus bits, I am aware that there is dbus support on Windows but not sure if it is needed for VYM (Windows). However, I don’t think this is a major issue for now.  
I have also read Patrick post about using emerge to reproduce the Windows build, so I will follow that  
Is Patrick still doing the Windows builds?  
I have looked at Clementine on Windows and they are using mingw, so I think you gut feeling is right J
I will look more into quzip and there is also OSDaB, have you considered it? 
Since, I depend on and love using VYM I am motivated to work on the Windows port. 
Best regards,
Hi Kais,
On Thu, Mar 07, Dr. Kais Hassan wrote:
> I have create a guide to help people with using VYM on Windows.
> http://kaismh.wordpress.com/2013/03/07/view-your-mind-vym-2-2-4-windows-setup-and-configuration/
Thanks a lot!!
> Also, I am interested in helping with the Windows port, fixing bugs, packaging and etc.
That's very much appreciated. In the past there have been several
attempts, but so far there is no continuos maintenance of the windows
While I wrote the very most of the vym code, I have no access to windows
machines, so I cannot help here.
> Which Qt for Windows should I use for the port (msvc or mingw)?
My gut feeling is to use mingw, maybe we could even set up cross
I usually build vym in my home project for various platforms:
The spaces in filenames seem to work for me in Linux, so probably
related to executing zip/unzip.
Btw. we probably could get rid of zip/unzip at least for Windows by
using quzip. I also tried using qCompress, but that slowed down
load/save of maps too much.
mathematician, n:
   Someone who believes imaginary things appear right before your i's.