Now, that is a different topic this time, ay?
The obligatory screenshot first:
Does it do anything? No currently not. Clicking on new causes it to crash inside some SQL code. But the port has been fun so far and basically is a perfect example of getting stuff to another platform (which I did before more than once, though I seldomly ported something to Windows yet). Usually you need to take care of dependencies and try to get those running first. It even gets more complicated, when you use a different compiler.
Above version is done with the Microsoft compiler, but unfortunately libofx is designed for MinGW in best case. Both have different ways, when it comes to exporting symbols. GCC usually exports everything, while msvc demands specification on this topic. Using static linking helped for now. Never the less, libofx needed some patches and it depends on OpenSP again, which needed to get some care as well. Well, not the lib itself, the included Windows makefiles are for Visual Studio 6 currently and they include some weird configuration like author names as namespaces and such.
What needs to be done next
- Get the emerge stuff cleaned up and committed
- Get the patches upstream
- Get Skrooge actually do something
Thanks to Patrick for his IRC-assistance and Guillaume for his pointers and help so far.