Honestly I can't even get a simple SWIG project working (the demo from
klickverbot's announcement on his blog). Apparently there's some
const-related issues.
Building the examples that come with swig windows binary doesn't work,
tried it via mingw32-make and via MSYS. Apparently there's a missing
"Makefile" in the root dir. Building SWIG from source doesn't work on
Windows anymore either. ("Swig/misc.c:1119:18: fatal error: pcre.h: No
such file or directory"). So you have a project that is only
maintained on some platforms. (this is the swig-2.0.4 release).
Funnily enough the SVN version from a year ago worked perfectly, but
now an official release doesn't work.
The question is, what if you end up finding a bug in the generated
code? Worst case scenario - you have to fix SWIG itself.
Btw, Johannes Pfau wrapped most of TagLib with SWIG and said the
wrapping process was frustrating.
I quite like the 'wxc' wrapper library, if you screw something up it
doesn't look like too much work to fix it. Obviously you have to write
everything by hand, so it's repetitive work. But at least you get a
readable codebase + you get to statically link with the library.
