Bill Baxter wrote:
On 4/5/07, Adib Taraben <taraben.a@...1512...> wrote:
Bill Baxter schrieb:
Thanks to the helpful hint about btool, I was able to build inkscape on Win32 this morning.
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
That packaged coexists as you need to unzip into C:/MinGW4 instead of C:/MinGW Later packages need to unzipped into C:/MinGW It was defined at compile times and are needed i.e. for the libs path.
Actually, unzipping it into C:\MinGW4 was what I did initially because I didn't want to clobber my existing setup. But I wasn't able to compile anything that way because g++ failed to find any of its headers (like <iostream> etc). After renaming the directory to C:\mingw everything worked fine.
So I'm pretty sure the C:\mingw path is embedded somewhere in the MinGW 4 package I downloaded from the net. (This is the one I'm using: mingw-4.1.2-070401)
For now I've resorted to just renaming the directory depending on whether I'm working on Inkscape or something else. Times like these I really wish Windows had symlinks.
--bb
This is something that seems to have happened recently, and did not bother us before. I saw a web page where a guy described a "relocatable" MinGW. I'll give that a try.
bob