Dev:Mingw installation
Contents
MinGW
First - download MinGW installer. You may get version 5.1.3 or higher (recommended).
Run MinGW-5.1.3.exe. Select "Download and install". Choose "Candidate" package, because "Current" is too old. When the installer asks which packages to install, select:
- MinGW base tools
- g++ Compiler
- g77 Compiler
- MinGW Make
Note: you really do need to install Fortran; even though Synfig does not require it, it is required by the autoconf configuration scripts. These are the minimal required package versions which are needed to successfully build win32 synfig:
- mingw-runtime-3.12.tar.gz (429.7 Kb)
- w32api-3.9.tar.gz (1.6 Mb)
- binutils-2.17.50-20060824-1.tar.gz (8.9 Mb)
- gcc-core-3.4.5-20060117-1.tar.gz (3.3 Mb)
- gcc-g++-3.4.5-20060117-1.tar.gz (4.5 Mb)
- gcc-g77-3.4.5-20060117-1.tar.gz (2.0 Mb)
- mingw32-make-3.81-2.tar.gz (95 Kb)
Confirm default installation path C:\MinGW. If you install MinGW into another directory, synfig compilation may fail.
MSYS
Now download and install MSYS - a shell and tools kit.
Run MSYS-1.0.10.exe, confirm default installation path C:\msys\1.0. Wait until installation completes. Then the installer opens a console and asks some questions.
This is a post install process that will try to normalize between
your MinGW install if any as well as your previous MSYS installs
if any. I don't have any traps as aborts will not hurt anything.
Do you wish to continue with the post install? [yn ]
Answer "y" here.
Do you have MinGW installed? [yn ]
Answer "y" here.
Please answer following the in the form of c:/foo/bar.
Where is your MinGW installation?
Answer "c:/mingw".
The installer script prints some text and finally writes:
Oh joy, you do not have c:/mingw/bin/make.exe. Keep it that way.
It's OK. The first phase of installation is completed. Press any key.
MSYS Developer Toolkit
Download MSYS Developer Toolkit, which contain such required tools as autoconf, automake, libtool, perl, pkg-tools, etc. Unfortunately, many tools included in MSYS DTK is too old and we need update it manually later.
Run msysDTK-1.0.1.exe. Confirm your MSYS installation path C:\msys\1.0. Nothing more. Installation will continue without any additional questions.
bash
The current bash version is not enough for Synfig building and neither is the new 2.05b version. It contains an error and you need to download 3.1 snapshot:
Make sure that all msys sessions are closed, then just decompress bash-3.1 directory from archive into C:\msys\1.0.
Also, you may want to edit C:\msys\1.0\msys.bat file. You may find string which contain if "x%MINGW32BGCOLOR%" == "x" set MINGW32BGCOLOR= and set Black as color. Into if "x%MINGW32FGCOLOR%" == "x" set MINGW32FGCOLOR= you may set color White. In string start rxvt -backspacekey you may replace -fn Courier-12 to -fn Courier-16. In my opinion this makes msys sessions look better.
autoconf
As written before, some tool are too old for Synfig build. For example, since revision 547 synfig required autoconf and automake, included in MSYS DTK are not acceptible. And we need replace them by new version.
Download new autoconf from:
Decompress content of archive to C:\msys\1.0 directory.
automake
Download new automake from:
Decompress content of archive to C:\msys\1.0 directory.
libtool
In Synfig Core bootstrap file we can find that libtool prior to version 1.4.2 has an error in libltdl but msys has only 1.4e. I think - will be better to update it instead of patching. Download libtool 1.5 from:
Decompress content of archive to C:\msys\1.0 directory.
mktemp
Synfig requires mktemp for building, but for some unknown reason this tool is not installed by default in MinGW. Download the MinGW implementation of this tool from:
Decompress mktemp.exe from this archive to C:\msys\1.0\bin directory.
file
libtool requires the "file" tool to check filetypes of libraries. So we need to download it:
and decompress content of directory file-4.16 from the archive to C:\msys\1.0.
cygpath emulation
As far as I read, Cygwin only supports paths like /C/somedir/somefile. MinGW can use native windows paths also. Cygwin has a special tool for this (and some another features). MinGW has not. But several Synfig configure scripts require this tool so it will be better to make it. Just save the following text as C:\msys\1.0\bin\cygpath:
#!/bin/sh
# A simple cygpath replacement
until [ -z "$1" ]
do
if [ "${1:0:1}" != "-" ]; then
echo $1 | sed -e 's/\\/\//g' -e 's/^\([a-zA-Z]\):/\/\1/g'
fi
shift
done
png2ico
Early version of Synfig used pngtoico tool to produce icons from png files. Unfortunately this tool is broken now. You can see this for youeself by installing the official build of Synfig Studio 0.61.05. The latest versions of Synfig using another tool: png2ico. This tool is not perfect, but it works. Download it from:
And decompress png2ico.exe file to C:\msys\1.0\bin directory.
Non MinGW packages
Subversion
Synfig source is stored in a subversion repository. You will need the svn client to get it. Also the svn client is required by the Synfig build scripts, to receive the revision number of the source. You can download the Windows subversion package from this page:
When I wrote this the latest version was 1.4.3:
But it is best to get the newest available version.
NSIS
NSIS is the Nullsoft Scriptable Install System, a free and open source installer for WinAmp, a popular windows music player. When I wrote this the latest version was 2.27:
You can use this or any newer version.
ImageMagick
When I wrote this the latest version was 6.3.4-10:
ImageMagick is required to build Studio, also Core has an ImageMagick render target.
Gtk+/Gtkmm
GTK+
Go to this page and download the latest GTK+ devel package for windows:
You need only install the following components:
- Gtk+ Runtime (required)
- Register Environment Variables
- Devel header/libraries
Confirm registration for environment: MSYS (C:\msys\1.0).
Install GTK+ to C:\GTK.
GTKmm
Go to this page and download the latest GTKmm devel package for Windows:
You need only install the following components:
- libsigc++
- cairomm
- glibmm
- gtkmm
- libxml++
For each selected component you may keep only
- Runtime
- Development
subcategories. Install GTKmm to C:\GTK.
Collision Resolution
If you have several Gtk-applications (f.e. InkScape), you can receive a strange errors, like "the procedure entry point XML_SetDoctypeDeclHandler could not be located in the dynamic link library xmlparse.dll". Thats mean you have an old version of this library in windows system32 directory, installed by another program. Just search and rename/delete this old library and all will work perfectly again.
