I decided to start my own topic about my journey of building Synfig for Windows.
DISCLAIMER: I’m not promise to be perfectly clear and answer all the questions in the thread - this is just a report to give you a picture what’s going on.
After playing with Fedora cross-compile environment I have managed to get first Windows builds of Synfig. But unfortunately they suffer some nasty glitches and I am not ready to fix them without trying other build methods.
So, my idea is to try build natively on Windows and see if I will have similar glitches. For the past 2 days I have discovered that there are dozen approaches to build Linux software on Windows - it’s MinGW/MSYS, MinGW-w64 (mxe.cc/), Yypkg, mgwport…
OMG, choosing a toolchain/environment is a challenge, especially when your time is limited (I need fresh binaries by June 29th). All those different approaches are mixed together and it really takes time to dig into all this.
I decided to go with Cygwin environment, as it looks very solid and well established (and have a lot of pre-compiled packages, compared to plain MinGW). But here choices as well! You can:
- compile directly in cygwin (then your build depend on cygwin.dll, which is not desirable)
- compile with MinGW on cywin toolchain
- compile with MinGW-w64 on cywin toolchain (it’s not the same as above!)
Since (3) is the same as I was already tried on Fedora, I would like to go with (2). There are already many dependencies precompiled and I can get more of them from sourceware.org/cygwinports/. But still some dependencies (like libxml++) are missing and I need to get compile them by myself.
Probably the best approach here is to use cygport. I.e. write my own *.cygport files and cleanly package all missing dependencies and synfig itself. (See gitorious.org/mgwport/mgwport/b … ORT.README).
Now I’m back to the fight.