|
|
| Line 36: |
Line 36: |
| | | | |
| | ===cygpath emulation(yet to fully check on this component)=== | | ===cygpath emulation(yet to fully check on this component)=== |
| − | 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]===
| |
| − | Early version of Synfig used [http://www.kernel.org/pub/software/graphics/pngtoico/ 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: http://www.winterdrache.de/freeware/png2ico/data/png2ico-win-2002-12-08.zip (89.9 Kb)
| |
| − | # And decompress png2ico.exe file to <code>'''C:\msys\1.0\bin'''</code> directory.
| |
| − |
| |
| − | ==Non MinGW packages==
| |
| − | ===[http://subversion.tigris.org Subversion]===
| |
| − |
| |
| − | Source code is now in GIT
| |
| − |
| |
| − | 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:
| |
| − |
| |
| − | * http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91
| |
| − |
| |
| − | 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]===
| |
| − | 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)
| |
| − |
| |
| − | You can use this or any newer version.
| |
| − |
| |
| − | ===[http://www.imagemagick.org ImageMagick]===
| |
| − | When I wrote this the latest version was 6.3.4-10:
| |
| − |
| |
| − | * http://www.imagemagick.org/download/binaries/ImageMagick-6.4.8-3-Q16-windows-dll.exe (11 MB)
| |
| − |
| |
| − | '''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==
| |
| − | ===[http://www.gtk.org/ GTK+]===
| |
| − | Go to [http://gladewin32.sourceforge.net/modules/news/ this page] and download the latest GTK+ devel package for windows:
| |
| − |
| |
| − | * http://gladewin32.sourceforge.net/modules/wfdownloads/visit.php?lid=110 (12 MB)
| |
| − |
| |
| − | ^^ These links are broken :( Pixelgeek is researching alternate solutions
| |
| − |
| |
| − | Though it's not yet tested, you can try either:
| |
| − | * http://downloads.sourceforge.net/gladewin32/gtk-dev-2.12.9-win32-2.exe (16.7 MB)
| |
| − | * http://downloads.sourceforge.net/gladewin32/gtk-dev-2.12.9-win32-1.exe (13,313 KB)
| |
| − |
| |
| − | 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 <code>C:\GTK</code>.
| |
| − |
| |
| − | ===[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:
| |
| − |
| |
| − | * http://ftp.gnome.org/pub/gnome/binaries/win32/gtkmm/2.10/gtkmm-win32-devel-2.10.8-1.exe (16.1 MB)
| |
| − |
| |
| − | If you opted for '''gtk-dev-2.12.9-win32-2.exe''' or '''gtk-dev-2.12.9-win32-1.exe''' pick this instead.
| |
| − | * 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 (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 <code>'''C:\GTK'''</code>.
| |
| − |
| |
| − | ===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
| |
| − |
| |
| − | ==MinGW(Old and unusable will be replaced as the new information is tested and added to the page)==
| |
| − | 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
| |
| − |
| |
| − | 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:
| |
| − |
| |
| − | * 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 (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)
| |
| − |
| |
| − | 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)
| |
| − |
| |
| − | ===MSYS===
| |
| − | 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.
| |
| − |
| |
| − | :<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>
| |
| − |
| |
| − | Answer "<code>'''y'''</code>" here.
| |
| − |
| |
| − | :<code>'''Do you have MinGW installed? [yn ]'''</code>
| |
| − |
| |
| − | Answer "<code>'''y'''</code>" here.
| |
| − |
| |
| − | :<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>: | | 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>: |
| | | | |
Welcome to the updated mingw page! As the information is checked to be fully functional we will post it to this page. As that is verified the old information shown here will be deleted since you are not what so ever to get it working using the below information since the developers of mingw have discontinued and removed that version and setup of that way completely. For now refer to this page: http://www.mingw.org/wiki/Getting_Started
First - download MinGW installer. You may get version mingw-get-inst-20101030.exe or higher but with the current setup of mingw this is best way to install it.
Run mingw-get-inst-20101030.exe(or what version you get). When the installer asks which packages to install, select:
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):
This is installed when you install mingw if you selected, if you feel so nesscary to install it open a mingw shell and run mingw-get install msys-base but this command might just be uncesscary
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:
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:
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:
ImageMagick is required to build Studio, also Core has an ImageMagick render target.
subcategories. Install GTKmm to C:\GTK.
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 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:
