Difference between revisions of "Dev:Mingw installation"

From Synfig Studio :: Documentation
Jump to: navigation, search
(→‎[http://subversion.tigris.org Subversion]: migrated to GIT!)
(→‎GTKmm)
 
(29 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
<!--Categories-->
 
<!--Categories-->
−
[[Category:Building]]
+
{{Category|Building}}
−
[[Category:Windows]]
+
{{Category|Windows}}
  
−
==MinGW==
 
−
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).
 
  
−
* https://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/MinGW-5.1.4.exe/download
+
==Updated Mingw==
 +
Welcome to the updated mingw page!
  
−
Run MinGW-5.1.4.exe. Select "Download and install". Choose "Candidate" package, because "Current" is too old. When the installer asks which packages to install, select:
+
Please you can also refer to this page: http://www.mingw.org/wiki/Getting_Started on how to install MingW
  
−
* MinGW base tools
+
Step 1 - Download [http://www.mingw.org/ MinGW] installer (mingw-get-setup.exe)
−
* g++ Compiler
+
Run mingw-get-setup.exe and follow the installation step (see Figure 1)
−
* 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 (version numbers from the 5.1.3 package):
+
Figure 1: MinGW Setup. You can uncheck the checkbox highlighted in green if you prefer to use the command line option to install the required MinGW packages (see Note 2)
 +
 
 +
[[File:Mingw-installation-step-1.png]]
 +
 
 +
 
 +
Step 2: Install the following packages using the MinGW Installer(see Figure 2)
 +
* MinGW Compiler Suit
 +
** C Compiler (selected always)
 +
** C++ Compiler (select it)
 +
** Fortran Compiler (select it)
 +
* MSYS Basic System (select it)
 +
* MinGW Developer Toolkit (select it)
 +
 
 +
Note 1: 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 (version numbers from the 5.1.3 package):
  
 
* mingw-runtime-3.12.tar.gz (429.7 Kb)
 
* mingw-runtime-3.12.tar.gz (429.7 Kb)
Line 25: Line 35:
 
* mingw32-make-3.81-2.tar.gz (95 Kb)
 
* mingw32-make-3.81-2.tar.gz (95 Kb)
  
−
Confirm default installation path <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.
 
  
−
(instructions updated from version 5.1.3 to 5.1.4, but untested.  please update the wiki if anything is broken with 5.1.4)
+
Figure 2: Installing the required packages
  
−
===MSYS===
+
[[File:Mingw-installation.PNG]]
−
Now download and install MSYS - a shell and tools kit.
+
  
−
* http://downloads.sourceforge.net/mingw/MSYS-1.0.10.exe (2.7 Mb)
 
  
−
Run MSYS-1.0.10.exe, confirm default installation path <code>C:\msys\1.0</code>. Wait until installation completes. Then the installer opens a console and asks some questions.
+
Note 2: Windows command line option for installing the required MinGW packages
 +
<pre> mingw-get.exe install gcc g++ fortran msys-base mingw-developer-toolkit </pre>
  
−
:<code>'''This is a post install process that will try to normalize between'''<br />'''your MinGW install if any as well as your previous MSYS installs'''<br />'''if any. I don't have any traps as aborts will not hurt anything.'''<br />'''Do you wish to continue with the post install? [yn ]'''</code>
+
Figure 3: package installation from the Windows command line
  
−
Answer "<code>'''y'''</code>" here.
+
[[File:Mingw-installation-cmd.PNG]]
  
−
:<code>'''Do you have MinGW installed? [yn ]'''</code>
+
Confirm default installation path <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.
  
−
Answer "<code>'''y'''</code>" here.
+
===MSYS===
−
 
+
This is installed when you install mingw if you selected, if you feel so necessary to install it open a mingw shell and run <code>mingw-get install msys-base</code> but this command might just be unnecessary
−
:<code>'''Please answer following the in the form of c:/foo/bar.'''<br />'''Where is your MinGW installation?'''<br /></code>
+
−
 
+
−
Answer "<code>'''c:/mingw'''</code>".
+
−
 
+
−
The installer script prints some text and finally writes:
+
−
 
+
−
:<code>'''Oh joy, you do not have c:/mingw/bin/make.exe. Keep it that way.'''</code>
+
−
 
+
−
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 [http://www.gnu.org/software/autoconf/ autoconf], [http://www.gnu.org/software/automake/ automake], [http://www.gnu.org/software/libtool/ libtool], [http://www.cpan.org/ perl], pkg-tools, etc. Unfortunately, many tools included in MSYS DTK is too old and we need update it manually later.
+
−
 
+
−
* http://downloads.sourceforge.net/mingw/msysDTK-1.0.1.exe (9.8 Mb)
+
−
 
+
−
Run msysDTK-1.0.1.exe. Confirm your MSYS installation path <code>C:\msys\1.0</code>. 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: * http://downloads.sourceforge.net/mingw/bash-3.1-MSYS-1.0.11-snapshot.tar.bz2 (538.2 Kb)
+
−
# Make sure that all msys sessions are closed,
+
−
# then just decompress bash-3.1 directory from archive into <code>C:\msys\1.0</code>.
+
−
 
+
−
Also, you might want to edit <code>'''C:\msys\1.0\msys.bat'''</code> file. If so, do the following:
+
−
{| class="wikitable" style="text-align:center"
+
−
|-
+
−
! Look into the string which contain !! Find !! Replace
+
−
|-
+
−
! <code>'''MINGW32BGCOLOR='''</code>
+
−
| <code>'''{Any Color}'''</code> || <code>'''Black'''</code>
+
−
|-
+
−
! <code>'''MINGW32FGCOLOR='''</code>
+
−
| <code>'''{Any Color}'''</code> || <code>'''White'''</code>
+
−
|-
+
−
! <code>'''start rxvt -backspacekey'''</code>
+
−
| <code>'''-fn Courier-12'''</code> || <code>'''-fn Courier-16'''</code>
+
−
|}
+
−
 
+
−
===[http://www.gnu.org/software/autoconf/ 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: http://downloads.sourceforge.net/mingw/msys-autoconf-2.59.tar.bz2 (394.7 Kb)
+
−
# Decompress content of archive to <code>'''C:\msys\1.0'''</code> directory.
+
−
 
+
−
===[http://www.gnu.org/software/automake/ automake]===
+
−
# Download new automake from: http://downloads.sourceforge.net/mingw/msys-automake-1.8.2.tar.bz2 (304 Kb)
+
−
# Decompress content of archive to <code>'''C:\msys\1.0'''</code> directory.
+
−
 
+
−
===[http://www.gnu.org/software/libtool/ 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: http://downloads.sourceforge.net/mingw/msys-libtool-1.5.tar.bz2 (411.3 Kb)
+
−
# Decompress content of archive to <code>'''C:\msys\1.0'''</code> directory.
+
−
 
+
−
=== [http://www.gnu.org/software/gettext Gettext] ===
+
−
Starting from SVN 1143, Synfig offers support for internationalization (languages translations). For this, Gettext is needed.
+
−
 
+
−
# You'll need [http://www.cygwin.com/ Cygwin] project's [http://cygwin.com/packages/gettext-devel/ gettext-devel] package: http://ftp.yz.yamagata-u.ac.jp/pub/cygwin/release/gettext/gettext-devel/
+
−
# Unpack the archive so that everything is under <code>'''/usr/local'''</code> instead of <code>'''/usr'''</code>.
+
−
 
+
−
'''Note:''' Any binaries that are not from the MinGW project (''or not built specially for MSYS'') cannot be placed in the <code>'''/msys/1.0/bin'''</code> (<code>'''/bin'''</code> and <code>'''/usr/bin'''</code> inside MSYS) directory. You then need to:
+
−
# hack the <code>'''/usr/local/bin/autopoint'''</code> script so that prefix is defined as <code>'''/usr/local'''</code> instead of <code>'''/usr'''</code>.
+
−
# '''Warning!''' Ugly hack follows
+
−
:: Autopoint expects to find an <code>'''archive.tar.gz'''</code> in <code>'''usr/share'''</code>, so copy gettext (found on <code>'''usr/share/'''</code> on the archive) file structure to <code>'''/usr/share'''</code> also.
+
−
 
+
−
'''Update:''' If you insist a MSYS-compatible gettext-devel, try: http://downloads.sourceforge.net/mingw/gettext-devel-0.16.1-MSYS-1.0.11-1.tar.bz2
+
−
* As of this post, <code>'''gettext-devel-0.16.1-MSYS'''</code> is being tested for problem-free Synfig compile.
+
−
 
+
−
'''Note:''' If you reload the GTK+ devel environment, make sure that you rename the autopoint script and gettext so that they don't conflict with the ones in msys. GTK\bin tends to show up first in the path, and those versions get picked by default.
+
−
 
+
−
===[http://www.mktemp.org/ 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: http://downloads.sourceforge.net/mingw/mktemp-1.5-MSYS.tar.bz2 (4 Kb)
+
−
# Decompress mktemp.exe from this archive to <code>'''C:\msys\1.0\bin'''</code> directory.
+
−
 
+
−
===[http://darwinsys.com/file/ file]===
+
−
libtool requires the "file" tool to check filetypes of libraries.
+
−
 
+
−
# So we need to download it: http://downloads.sourceforge.net/mingw/file-4.16-MSYS-1.0.11-snapshot.tar.bz2 (236.2 Kb)
+
−
# Decompress content of directory file-4.16 from the archive to <code>'''C:\msys\1.0'''</code>.
+
−
 
+
−
===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 <code>C:\msys\1.0\bin\cygpath</code>:
+
−
 
+
−
<pre>#!/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</pre>
+
  
 
===[http://www.winterdrache.de/freeware/png2ico/index.html png2ico]===
 
===[http://www.winterdrache.de/freeware/png2ico/index.html png2ico]===
Line 148: Line 60:
  
 
==Non MinGW packages==
 
==Non MinGW packages==
−
===[http://subversion.tigris.org Subversion]===
+
=== [http://git-scm.com/ Git] ===
 +
Synfig source is now stored in a git repository (https://github.com/synfig/synfig) - you can use [https://github.com/blackwarthog/synfig.git blackwarthog's] fork. You will need the git client to get it. Also, git is needed by the build scripts to receive the revision number of the source.
 +
You can download the Windows git version from one of these page:
  
−
Source code is now in GIT
+
* http://git-scm.com/download
 +
* http://msysgit.github.io
  
−
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.
+
Get always the latest version available (version 1.9.5, link updated August 2015):
−
You can download the Windows subversion package from this page:
+
* https://github.com/msysgit/msysgit/releases/download/Git-1.9.5-preview20150319/Git-1.9.5-preview20150319.exe
  
−
* http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91
+
After download and install (I recommend to install to custom folder C:\Git) you must add C:\Git\bin to the PATH. See here to know how to do that. http://www.mingw.org/wiki/Getting_Started (Environment Variables).
−
 
+
−
When I wrote this the latest version was 1.4.3:
+
−
 
+
−
* http://subversion.tigris.org/files/documents/15/36797/svn-1.4.3-setup.exe (3.58 Mb)
+
−
 
+
−
But it is best to get the newest available version.
+
  
 
===[http://sourceforge.net/projects/nsis/ NSIS]===
 
===[http://sourceforge.net/projects/nsis/ NSIS]===
 
NSIS is the Nullsoft Scriptable Install System, a free and open source installer for WinAmp, a popular windows music player.
 
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:
 
  
−
* http://downloads.sourceforge.net/nsis/nsis-2.42-setup.exe (1.4 Mb)
+
The latest version as of August 2015 is 2.46:
 +
* http://downloads.sourceforge.net/nsis/nsis-2.46-setup.exe (1.6 Mb)
  
 
You can use this or any newer version.
 
You can use this or any newer version.
Line 198: Line 107:
 
* Devel header/libraries
 
* Devel header/libraries
  
−
Confirm registration for environment: ''MSYS (C:\msys\1.0)''.
+
Confirm registration for environment: ''MSYS (C:\mingw\msys\1.0)''.
  
 
Install GTK+ to <code>C:\GTK</code>.
 
Install GTK+ to <code>C:\GTK</code>.
  
 
===[http://www.gtkmm.org/ GTKmm]===
 
===[http://www.gtkmm.org/ GTKmm]===
−
Go to [http://www.pcpm.ucl.ac.be/~gustin/win32_ports/ this page] and download the latest GTKmm devel package for Windows:
+
maybe this is useful to read too: http://live.gnome.org/gtkmm/MSWindows
 +
Go to [https://wiki.gnome.org/Projects/gtkmm/MSWindows this page] and download the latest GTKmm devel package for Windows:
  
 
* http://ftp.gnome.org/pub/gnome/binaries/win32/gtkmm/2.10/gtkmm-win32-devel-2.10.8-1.exe (16.1 MB)
 
* http://ftp.gnome.org/pub/gnome/binaries/win32/gtkmm/2.10/gtkmm-win32-devel-2.10.8-1.exe (16.1 MB)
Line 210: Line 120:
 
* ftp://ftp.gnome.org/pub/GNOME/binaries/win32/gtkmm/2.10/gtkmm-win32-devel-2.10.11-1.exe (16.3 MB)
 
* ftp://ftp.gnome.org/pub/GNOME/binaries/win32/gtkmm/2.10/gtkmm-win32-devel-2.10.11-1.exe (16.3 MB)
  
−
You need only install the following components:
+
You need only install the following components (footnote 1):
  
 
* libsigc++
 
* libsigc++
Line 217: Line 127:
 
* gtkmm
 
* gtkmm
 
* libxml++
 
* libxml++
 +
 +
(1) if you're using gtkmm-win32-devel-2.16.0-4.exe, then pangomm is a required component. 
  
 
For each selected component you may keep only
 
For each selected component you may keep only
Line 227: Line 139:
 
===Collision Resolution===
 
===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.
 
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.
 +
 +
===Troubleshooting===
 +
Test whether MSYS can find MinGW by running:
 +
 +
$ gcc --version
 +
 +
If it replies command not found, MSYS can't see MinGW. In that case, you will need to edit the text file C:\msys\1.0\etc\fstab so that it includes the line:
 +
 +
c:/MinGW /mingw

Latest revision as of 13:05, 19 October 2015


Updated Mingw

Welcome to the updated mingw page!

Please you can also refer to this page: http://www.mingw.org/wiki/Getting_Started on how to install MingW

Step 1 - Download MinGW installer (mingw-get-setup.exe) Run mingw-get-setup.exe and follow the installation step (see Figure 1)

Figure 1: MinGW Setup. You can uncheck the checkbox highlighted in green if you prefer to use the command line option to install the required MinGW packages (see Note 2)

Mingw-installation-step-1.png


Step 2: Install the following packages using the MinGW Installer(see Figure 2)

  • MinGW Compiler Suit
    • C Compiler (selected always)
    • C++ Compiler (select it)
    • Fortran Compiler (select it)
  • MSYS Basic System (select it)
  • MinGW Developer Toolkit (select it)

Note 1: 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 (version numbers from the 5.1.3 package):

  • 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)


Figure 2: Installing the required packages

Mingw-installation.PNG


Note 2: Windows command line option for installing the required MinGW packages 

 mingw-get.exe install gcc g++ fortran msys-base mingw-developer-toolkit

Figure 3: package installation from the Windows command line

Mingw-installation-cmd.PNG

Confirm default installation path C:\MinGW. If you install MinGW into another directory, synfig compilation may fail.

MSYS

This is installed when you install mingw if you selected, if you feel so necessary to install it open a mingw shell and run mingw-get install msys-base but this command might just be unnecessary

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.

  1. Download it from: http://www.winterdrache.de/freeware/png2ico/data/png2ico-win-2002-12-08.zip (89.9 Kb)
  2. And decompress png2ico.exe file to C:\msys\1.0\bin directory.

Non MinGW packages

Git

Synfig source is now stored in a git repository (https://github.com/synfig/synfig) - you can use blackwarthog's fork. You will need the git client to get it. Also, git is needed by the build scripts to receive the revision number of the source. You can download the Windows git version from one of these page:

Get always the latest version available (version 1.9.5, link updated August 2015):

After download and install (I recommend to install to custom folder C:\Git) you must add C:\Git\bin to the PATH. See here to know how to do that. http://www.mingw.org/wiki/Getting_Started (Environment Variables).

NSIS

NSIS is the Nullsoft Scriptable Install System, a free and open source installer for WinAmp, a popular windows music player.

The latest version as of August 2015 is 2.46:

You can use this or any newer version.

ImageMagick

When I wrote this the latest version was 6.3.4-10:

Note: The updated file has not been tested yet -- try here instead http://www.imagemagick.org/download/www/binary-releases.html#windows

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:

^^ These links are broken :( Pixelgeek is researching alternate solutions

Though it's not yet tested, you can try either:

You need only install the following components:

  • Gtk+ Runtime (required)
  • Register Environment Variables
  • Devel header/libraries

Confirm registration for environment: MSYS (C:\mingw\msys\1.0).

Install GTK+ to C:\GTK.

GTKmm

maybe this is useful to read too: http://live.gnome.org/gtkmm/MSWindows

Go to this page and download the latest GTKmm devel package for Windows:

If you opted for gtk-dev-2.12.9-win32-2.exe or gtk-dev-2.12.9-win32-1.exe pick this instead.

You need only install the following components (footnote 1):

  • libsigc++
  • cairomm
  • glibmm
  • gtkmm
  • libxml++
(1) if you're using gtkmm-win32-devel-2.16.0-4.exe, then pangomm is a required component.

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.

Troubleshooting

Test whether MSYS can find MinGW by running:

$ gcc --version

If it replies command not found, MSYS can't see MinGW. In that case, you will need to edit the text file C:\msys\1.0\etc\fstab so that it includes the line:

c:/MinGW /mingw

Retrieved from "https://wiki.synfig.org/index.php?title=Dev:Mingw_installation&oldid=20907"