Hi,
I was away for a day or so. Sorry I missed this thread.
Bill Baxter wrote:
Thanks to the helpful hint about btool, I was able to build inkscape on Win32 this morning.
I have promised to update that about 10 times or so. I really will, I swear. I have some kind of weird writer's block concerning that file.
Questions:
- does anyone know if MinGW 4.0 build from here http://wiki.inkscape.org/wiki/index.php/Win32Port
can peacefully coexist with the official MinGW package? I mean is it safe to unzip that MinGW directory right on top of the MingGW 3.4.5 installed by the official package from here: http://sourceforge.net/project/showfiles.php?group_id=2435
Basically, no. In addition to the normal rule that the .h's must match the libs, there are also inconsistencies in the C++ .h files. The GCC guys say that you -never- install one on top of the other. You can have problems not only with linking, but also with C++ compiling. This is why G++'s have their C++ dirs versioned. Also, the MinGW guys are in the process of switching from sjlj exceptions (setjump()/longjump()) to Dwarf exception handling (Dwarf EH). Libs made with one exception handling scheme don't mix with the other.
My main concern is that the 4.1 package is missing some things I'd like to have like g77 and gdb.
Building your own gcc was once very difficult, but not anymore. You can make it with MSYS:
tar zxf gcc-4.1.2-whatever.tar.gz cd gcc-4.1.2 mkdir objdir cd objdir ../configure --target=i686-pc-mingw32 --prefix=/mingw --with-sjlj-exceptions \ --enable-languages=c,c++,f77 make make install
....or leave out the languages option to get the defaults.
In msys's etc/fstab file, I have /mingw aliased to c:/mingw
With MSYS, make sure to use their version of make, not the one in MinGW. And you do need that sjlj flag to be compatible with the "official" mingw, and our C++ libs, like gtkmm or libsigc++. I want to switch ours, too, when it is safe.
1b) [OT] Ok, what's up with MinGW releases? Why isn't gcc 4.1 available from mingw.org itself?
Because of the Dwarf EH move, they wanted to wait until gcc-4.x was very stable before moving to that one. You might want to ask Danny Smith (the mingw gcc guy) about that. What is good is the fact that he is now one of the main GCC committers, so mingw is no longer a fringe product but a major subscriber.
- In the version I built, the Selection tool handles come out looking
like trashed and/or misaligned memory. Is this a known issue? Both sets of handles (scale and rot/shear) are messed up. All other handles for the other tools seem to be ok. (To repro, hit 'p', draw a curve, hit space.)
This sounds like either you have mixed Gtk libs, or that maybe you have another installation of gtk in your path.
- I can't seem to load any images in my build (like .bmp, .png etc.).
[Using the import menu item]
Same thing, maybe. GdkPixbuf has image loader modules in its lib directory, and they will silently fail if they can't find the version of libpng.dll, jpeg.dll, tiff.dll, etc, that they want.
- "Save window geometry" doesn't. Inkscape always opens up at the
same too-small default size whether I have the preference set or not. (That's true for the current release as well as my SVN build). Where would I start looking to go about fixing that?
You might try deleting your preferences file from your homedir in /Documents and Settings, and try again.
bob