Re: [Inkscape-devel] Building Inkscape on Win32
Johan wrote:
Currently we use 'buildtool' to build Inkscape on windows, which works perfect. Should we therefore still keep Makefile.mingw and its friends up to date? I cannot 'make' Inkscape with gtk210 because "-I$(GTK)/include/cairomm-1.0 " is missing in the include paths. When added it works fine, for the first files, but compilation stops at /dom/io/socket.cpp (plus i get a GLIBMM_DLL redefinition warning for a lot of files)
Also, I tried the latest build from http://inkscape.modevia.com/ and it crashes when the global pref window is opened.
Lots of build problems right before the release :S
Note that when I do 'buildtool dist' I get no errors and a nice working Inkscape distribution (that does not crash on opening pref dialog), but with the locale language files not properly copied.
- Should 'make' be made to work properly on Windows. If yes,
with gtk2.10 of gtk2.8? 2. inkscape.modevia.com crosscompiles I think; does that cause the crashes on pref. dialog?
Note that it is not that hard to get correct builds from 'make': only Makefile.mingw.common has to be updated a bit which was real easy. My question is therefore: should this be done in future and be committed to SVN? Maybe only for this release for the last time? And then after the release, delete all mingw makefiles, so there is no confusion anymore?
On 1/11/07, J.B.C.Engelen@...1578... <J.B.C.Engelen@...1578...> wrote:
Currently we use 'buildtool' to build Inkscape on windows, which works perfect. Should we therefore still keep Makefile.mingw and its friends up to date?
Hey, maybe this explains the weird blur-quantization bug also? I was always testing modevia Windows builds, which are done with the old method as I understand - whereas you're building it for yourself with buildtool, right? Maybe that's why you are seeing this bug and I'm not? No idea of what may cause such difference, though.
Bulia wrote:
On 1/11/07, J.B.C.Engelen@...1578... <J.B.C.Engelen@...1578...> wrote:
Currently we use 'buildtool' to build Inkscape on windows, which works perfect. Should we therefore still keep
Makefile.mingw and its
friends up to date?
Hey, maybe this explains the weird blur-quantization bug also? I was always testing modevia Windows builds, which are done with the old method as I understand - whereas you're building it for yourself with buildtool, right? Maybe that's why you are seeing this bug and I'm not? No idea of what may cause such difference, though.
I just succeeded in building inkscape the old way ('make'), and the "blur-quantization bug" is still present.
On 1/11/07, J.B.C.Engelen@...1578... <J.B.C.Engelen@...1578...> wrote:
I just succeeded in building inkscape the old way ('make'), and the "blur-quantization bug" is still present.
Hmm. Anyway, has anyone ever seen this on Linux, or is this a Windows-only bug?
On Thu, Jan 11, 2007 at 01:03:51PM -0400, bulia byak wrote:
On 1/11/07, J.B.C.Engelen@...1578... <J.B.C.Engelen@...1578...> wrote:
I just succeeded in building inkscape the old way ('make'), and the "blur-quantization bug" is still present.
Hmm. Anyway, has anyone ever seen this on Linux, or is this a Windows-only bug?
If this is the blur widget issue, I tried it on Linux on a dual 3GHz x86 gentoo box with gtk2.8, and could not reproduce the behavior.
Bryce
Is it possible that this is related to some other system parameters? colour depth, DivX version ?
Is it the same for an PNG output?
Adib. ...
bulia byak schrieb:
On 1/11/07, J.B.C.Engelen@...1578... <J.B.C.Engelen@...1578...> wrote:
I just succeeded in building inkscape the old way ('make'), and the "blur-quantization bug" is still present.
Hmm. Anyway, has anyone ever seen this on Linux, or is this a Windows-only bug?
participants (4)
-
unknown@example.com
-
Adib Taraben
-
Bryce Harrington
-
bulia byak