I skipped womens' gymnastics tonight, instead engaging in one of my dork activities, compiling and fiddling with software. I think I took home a bronze.
You can instead take home my windows installer for the gccxml compiler.
gccxml-0.9.0-win32-x86.exe [sig] [my gpg public key]
Work has been kicking me in the ass. Specifically, I want to use some libraries that work with the game and tools from python. Since I had an awesome (by which I mean fast as hell) time binding the Xbox 360 development libraries with ctypes via gccxml, I thought it would be just that easy this time around.
Enter boost.
You can instead take home my windows installer for the gccxml compiler.
gccxml-0.9.0-win32-x86.exe [sig] [my gpg public key]
Work has been kicking me in the ass. Specifically, I want to use some libraries that work with the game and tools from python. Since I had an awesome (by which I mean fast as hell) time binding the Xbox 360 development libraries with ctypes via gccxml, I thought it would be just that easy this time around.
Enter boost.
Or rather, the boost headers.
I should point out here that my core programming skills revolve around build systems, scripting languages, trouble shooting, pre flighting. None of which involves c++, nor meaty template code much. Which I was about to hit full speed.
It turns out, older versions of gccxml were not very boost-happy. The links escape me at home, but at work, there were plenty of hits regarding boost template instantiation and other errors. There was a patch, of sorts. Unfortunately, we're on an older version of boost. And apparently, the ctypes authors are still on an October 2006 version of gccxml. Boo. I got plenty of warnings as errors. Memo to self: disable warnings as errors and try again.
I integrated the latest boost partially, but wasn't up to much more than fixing some header references. Typically, when looking through boost or STL calls in the callstack, I just read above and below the layer where it hits it. So when I hit shit city, I p4tar'd up my change and reverted.
But there isn't any gccxml win32 installer dist for download that I could see besides the ctypes one. So I made one at home to try out at work tomorrow. Maybe it just works.
The gccxml directions are a little obtuse. But as luck would have it, I am fluent in obtuse. And I have a bevy of build tools hooked up to the Eclipse IDE. I ended up having to:
I should point out here that my core programming skills revolve around build systems, scripting languages, trouble shooting, pre flighting. None of which involves c++, nor meaty template code much. Which I was about to hit full speed.
It turns out, older versions of gccxml were not very boost-happy. The links escape me at home, but at work, there were plenty of hits regarding boost template instantiation and other errors. There was a patch, of sorts. Unfortunately, we're on an older version of boost. And apparently, the ctypes authors are still on an October 2006 version of gccxml. Boo. I got plenty of warnings as errors. Memo to self: disable warnings as errors and try again.
I integrated the latest boost partially, but wasn't up to much more than fixing some header references. Typically, when looking through boost or STL calls in the callstack, I just read above and below the layer where it hits it. So when I hit shit city, I p4tar'd up my change and reverted.
But there isn't any gccxml win32 installer dist for download that I could see besides the ctypes one. So I made one at home to try out at work tomorrow. Maybe it just works.
The gccxml directions are a little obtuse. But as luck would have it, I am fluent in obtuse. And I have a bevy of build tools hooked up to the Eclipse IDE. I ended up having to:
- import the gccxml module from cvs as a new eclipse project.
- make sure mingw and msys were installed (they were)
- grab cmake
- configure cmake from the start menu shortcut.
- Don't choose the beta.
- Check the 'Suppress dev warnings' box.
- Make sure your 'Where to build the binaries' directory is not in the source tree
- Make sure your 'Where is the source code' directory is the directory above GCC_XML and GCC
- Select the empty CMAKE_BUILD_TYPE field and set it to Release
- Press the configure button.
- Press the OK button.
- go back and install the c++ parts of the IDE (the eclipse CDT) into eclipse from the Europa discovery site.
- restart the IDE and build the project, not from the gccxml source module, but from the new cmake project that was made from step 4.
- also make the install/strip target.
- make sure NSIS is already installed (it was)
- also make the package target. Eclipse got confused and thought targets were up to date, so I restarted the IDE and it allowed me to select from the Makefile targets available.
Oh! Boost upgrade at work by senior engineer. Must try again.