luminarious wrote:Offtopic, but this sounds cool in a sunglasses-and-long-coat-fluttering-in-the-wind kind of way..
That's sounds far better then the actuality, which is me pouring though documentation, trying to figure out a way for mingw-gcc to compile a program in a way that satisfies both autoconf and python. The occasional curse may have been uttered.
Anyway, my current task is to try to get Ren'Py building on three platforms. This is made a little more difficult by my deciding that I would bump the version of Python we use to 2.6.5, so that we can take advantage of various bug fixes and performance improvements.
Linux is always the easy the platform. Half of it is because it's my main development platform, but mostly it's because Linux has its act together when it comes to libraries. No DLL hell here.
Mac was the second system I tried. There were the usual problems as I convince the compiler to do multi-architectures builds properly. And a lovely hard-coding of /usr/bin/arch in the Python build scripts, just to make the build process that much harder.
Windows is the land of DLL hell, and every time Microsoft tries to deal with it, they make it worse. The problem of the day is that Python is now built using libmsvcr90, which requires that you add a small XML document into every program you make. This is pretty easy to do - unless it's not you making the program, but autoconf.
The solution wound up being to change the GCC spec file to link the XML document in every time a program is compiled. But that took a day to come up with - and I have no idea why MS adopted such a complicated solution, when Linux has had a simple elegant one for 15 years or so.
Anyway, right now, Windows is busy building it's various dependencies. So hopefully, I'll be able to begin testing Ren'Py tomorrow.