Kees Cook schrieb:

Oh, I'm answering my own question. Here is where ishmal put the build notes:

http://inkscape.org/win32/win32buildnotes.html

I need someone to go through these steps and verify the build (I don't have cycles right now).

I will not repeat everything I will only mark differences or things that are not mentioned I added a target dist-strip that depends on dist and then strips the exe and some dlls from the debug info and removes unused files as gdb, header files and cvs-infos. This target should be used for the installer. The target dist is should still used for the daily build with the debug info Windows: -Makefile.mingw.common and mingwenv.bat assumes that there is: - c:\mingw\ with the mingw compiler package and - c.\gtk26\ with the latest gtk developer package - perl must be callable (means in the PATH) I do different on windows different: - I do not copy mingw32-make.exe into make.exe as I have some other make.exe versions on my computer - I call mingw32-make -f Makefile.mingw - I call mingw32-make -f Makefile.mingw dist or - I call mingw32-make -f Makefile.mingw dist-strip

Linux (DEBIAN) -I installed the mingw set on the Debian way: apt-get mingw32 It installed the mingw binaries in the callable path under /usr/bin etc. so there was no need to modify the path with the xmingw stuff. the compiler is i586-mingw32msvc-g++ the Makefile.mingw.common assumes that it is i686-pc-mingw32-g++ so I had to modify that.

-I unpacked the gtk libs into /home/adib/gtk26. I am not root so I can not make a /target directory so I had to go again to Makefile.mingw.common and tweak that setting on the line GTK=/home/adib/gtk26

-I have to prepare the environment only with export PKG_CONFIG_PATH=/target/lib/pkgconfig as I do not have to modify the path

-compilation was the same: make -f Makefile.mingw make -f Makefile.mingw dist or make -f Makefile.mingw dist-strip

HTH,

Adib.