Jon A. Cruz wrote:
On May 18, 2006, at 2:06 AM, Ralf Stephan wrote:
Regarding libsigc++ versions, inkscape compiles with 2.0.12 and gcc-4.0.2. Together with Jon Cruz' result with 2.0.11 and gcc-3, version 2.0.12 and up should be safe in all combinations.
Since this is still a year old, requirement is now libsigc++ >= 2.0.12
Eek!
I didn't foresee the problem. Since sigc++ 2.0.12 works fine with me here with gcc 3.3, that change just made Inkscape stop building for me.
:-(
I can probably change that locally for myself here, but is there some way we can get that conditional based on the gcc version so that we'll not block other people from being able to build?
I have been worried about this, since Mingw is currently at 3.4. Not only this, but we haven't updated our C++ libs in general for many months now. And 3.4 is allowing warnings and errors into the tree that unfairly plague others who have 4.x.
Also, the Mingw project shows no indication of releasing a fresh compiler in the near future. They usually wait until a GCC version is stable, but 4.x seems very stable.
So I spent the past two days locked indoors until I got both a cross compiler and a native compiler for GCC 4.1.1 (released Wednesday) built and uploaded.
Native: http://inkscape.modevia.com/win32libs/mingw411-060525.zip (unpacks to c\mingw4 to avoid conflict with official mingw)
Cross: http://inkscape.modevia.com/win32libs/xmingw-4.1.1.tar.bz2 (unpacks to /usr/local/xmingw)
Both seem to compile Inkscape quite well, and I have seen no ABI problems with the gtk28 bundle's C++ stuff like sigc++ or gtkmm. In fact, they seem to be faster compilers than gcc3.4, so using them is quite pleasant. And, yes, they show a waterfall of warnings (a good thing).
I guess I can work on the C++ libs after the release. Besides, I've been watching builds for two days and I have a headache. :)
bob