Synfig Studio :: Documentation - User contributions [en]

User:Creek23

2009-06-23T07:06:40Z

Creek23: /* Creek23 */ fixed link

== Creek23 ==
Just another [http://www.youtube.com/watch?v=HPLPQN57hk0|random animator] trying to help Synfig community with development, documentation, and such.

Developer of a [http://www.konsolscript.org | yet-to-become-useful scripting language]. :D

=== TODO ===
==== Development ====
* Learn to compile Synfig on Windows
* Try hacking the source code
==== Documentation ====
* Update [[Mingw installation|MinGW Installation]]
* Make tutorial.
==== Misc ====
* Make animation demo (bubbles).

User:Creek23

2009-01-11T22:54:58Z

Creek23: initial writeup

== Creek23 ==
Just another [http://www.youtube.com/watch?v=HPLPQN57hk0|random animator] trying to help Synfig community with development, documentation, and such.

Developer of a [http://konsolscript.sourceforge.net| yet-to-become-useful scripting language]. :D

=== TODO ===
==== Development ====
* Learn to compile Synfig on Windows
* Try hacking the source code
==== Documentation ====
* Update [[Mingw installation|MinGW Installation]]
* Make tutorial.
==== Misc ====
* Make animation demo (bubbles).

Dev:Wish list

2009-01-09T19:42:47Z

Creek23: /* Misc */ added splash screen; tagged done to two wishlist

'''''Warning''''': We need more people working on the code if we are going to be able to achieve all the feature requests.

Got a great idea for a new feature? Just add it here, or on the [http://sourceforge.net/tracker/?group_id=144022&atid=757419 feature requests tracker]. Before you do, please check the [https://synfig.svn.sourceforge.net/svnroot/synfig/ETL/trunk/TODO etl], [https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-core/trunk/TODO synfig] and [https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-studio/trunk/TODO synfigstudio] TODO files for similar ideas. Please add a rating of how essential this feature is to your workflow according to the following scale:

#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

== Misc ==

Please clean this section up as desired.

* A different color dialog for picking/changing colors easier.
** A color wheel like inkscape has (or the same) [done]
** Swatch menu from gimp with .gpl files.
* Workflow improvements, like content help and ui-refinement.
** set the fine line between design and animation work.
** Greet the user at startup, give hints and help in the ui to better the usability and user-experience.
* test synfig cross-platform (Linux, Windows, Mac)
* Installer for windows [done]
* Pluggable App (run from memory stick)
* make a short film about synfigs capabilitys in a starwars kind of spaceship setting as promo video about 3 minutes long.
* Sound layer
* full tablet support
* small set of vector contend for fast animation results
* Help is available as pdf-file and distributed with the program

'''Input:'''
* Import rastergraphics png, jpg, tif [done]
* Import vectorgraphics (svg,fig)

'''Output:'''
* Render output to animated gif [done]
* Render output to png, bmp, OpenEXR [done]
* Export vectorgraphics (svg,fig)

== Interchangeable/customizing Splash screen ==
[3] GIMP has this feature of letting users [http://docs.gimp.org/2.2/en/using-customize-splashscreen.html|customize GIMP's splash screen]. GIMP looks for <code>'''samples'''</code> directory under <code>'''.gimp-2.x'''</code> then randomly picks a picture from it to become the spash image.

This will also help GNU/Linux distro, like Ubuntu, to adopt Synfig and put their logo on the splash screen.

Also, official Synfig distribution can pack sample arts created by other artists to be randomly displayed -- like the synfig.org's title's background image.

== Verbosity levels for error output ==

Synfigstudio needs verbosity levels for the error output. Levels are info, warning and error. Make sure, to spew out only errors when something nasty happens. If someone wants to know all what happens in synfigstudio, the user should activate a higher level of verbosity with the command line switch --verbose=all,info,warning

== Usage screen for new users ==

Synfig and Synfigstudio need a usage screen, which helps a new user to type in the right syntax on the command line. Any switch not known to the program should point to the usage screen. On the bottom of the usage screen could be a hint: " For more help use synfig --help"

== Keyboard shortcuts for panning ==

The navigation and canvas windows need shortcut keys that pan the canvas view horizontally and vertically. Probably just the arrow keys would work for this, as well as the home/end/pageup/pagedown keys. Ctrl and shift variants could make the panning more or less.
: You can pan with a middle mouse button. --[[User:Zelgadis|Zelgadis]] 00:59, 24 October 2008 (EDT)

== Linking Zoom layer to Paste Canvas ==

[3] It is impossible to link Center of Zoom layer to Origin of Paste Canvas without exporting a value. It often needed for pans & zooms. Suggestion: rename "Center" parameter of Zoom Layer to the "Origin". Will improve the workflow. --[[User:Zelgadis|Zelgadis]]

== Convert Strings ==
[4] It could be very good to have feature to represent Convert sequences as strings and vice versa - make convert sequences from strings. Example: To produce this convert sequence:

[[Image:WishList-ConvertStrings.png]]

I just right-click on "Origin" parameter and choosing "String Convert" menu item. In the appeared dialog I just entering: "=Composite(Scale(x, Switch(scalar, 1.0, 0)), y)".

Also if I clicking on the parameter already containing convert sequence and choosing "String Convert", it shows string representation of current convert sequence with an ability to edit.

This feature will make possible to easy copy convert sequences from one parameter to another. --[[User:Zelgadis|Zelgadis]] 03:46, 2 November 2008 (EST)

== Non scalable timeline ==
[3] It should be useful for me to have non scalable timeline. It's hard to set timing when the distance between frames is always different in different documents and in different situations. Suggestion: make a non-scalable mode for timeline, where 1 second interval is always the same. Will improve the workflow. --[[User:Zelgadis|Zelgadis]]

==Smart linking of tangents==
[4] As described in [[Sewing BLines]], when linking red tangent to yellow they are placed opposite against each other. This is normal from the program's point of view, but not normal for new users. Even more, to avoid this effect user needs to made some complex steps (see [[Sewing BLines#Solution]]). It takes a lot of time if we vahe lot of verticles to sew their tangents.

Suggestion:
* When linking tangents with the same color, program should act as usual.
* When linking tangents with different color program should automaticaly add Convert->Scale (-1) to avoid their opposite placement.
To allow linking two tangents in opposite position, I suggest to add a new menu option for tangents "Link Opposite". When linking two tangents with this option:
* When linking tangents with the different color, program should act as it acts now - no additional converts added.
* When linking tangents with the same color program should automaticaly add Convert->Scale (-1) to plcae them opposite against each other.

--[[User:Zelgadis|Zelgadis]]

==Movement blur effect==
To make the motion most realistic for movies, it should be possible to activate in the render dialog the option to smear the border of all objects, which move faster than a given value. For example, if a ball gets shot over the canvas/rendering-screen with speed over 50 px/frame it should have a blurry streak attached. This effect could be applied only at rendering time as an after-effect. --[[User:SvH|SvH]] 09:50, 28 May 2008 (EDT)

:There is a [[Motion Blur Layer]] that you can apply to the entire document or to the layers you want. It allows to turn the blur effect on and off during animation. I think it is more flexible that your proposal. [[User:Genete|Genete]] 10:13, 28 May 2008 (EDT)

==Morph sets==
This feature is similar to some other suggestions below, just with another way to approach. In animations are many movements, which can be put in some kind of library, to make use of at a later time. For example, movements to animate the key moments of a mouth, sampling syllables. For vector graphics, it should be possible to define some key points, which move just a small amount of space, to form another syllable. These syllables in this example, should be stored in a drop down list, to be able to select them for the key time on the timeline.
A morph-set for walking-left-to-right is different from a morph-set for a mounth, which has as options a,e,i,o,u,bah-disgust,happy-smile. The morph-set has to be stored as vector coordinates in a relative way(offset), e.g. X1=+212,+34;X2=-56,-23;X3=+3,-88;

To make use of the morph-set for the mouth, you have to define first, which vector points in your drawn mouth, correspond to the key-points of your morph-set. X1, X2, X3, Xn

--[[User:SvH|SvH]] 06:53, 27 May 2008 (EDT)

==Render time approximation==
Synfigstudio should get a button in the render dialog, which calculates the total render time for the actual settings (frames per second, length of the film, resolution, output format) It should testrender 1 picture, when the amount of total frames is below 1000. Over 1000 frames, it should testrender 10 pictures for more precise calculation.

--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)

==Smartrendering==
I have made 25,000 small png-pictures with my 800Mhz computer in about 45 minutes. Synfigstudio did calculate each single frame of it. Nothing changed in this picture, so it does only need to get written to disk for the amount of pictures, until the next change (animation) has an effect on the output picture. This should save time for bigger projects with thousands of pictures. With smartrendering it is also possible to predict the total amound of space in Megabytes (Mibibytes) of the final render of the movie. It should calculate how much it needs and see, if enough space is free on the harddisk before the rendering get started.

--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)

== get_color method in text and radial blur ==

[5] Without get_color method distorion produces artifacts
[http://sourceforge.net/tracker/index.php?func=detail&aid=1831355&group_id=144022&atid=757416 bug 1831355]. So I would like to get this problem fixed before doing something else. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)

== Full functional of group dialog ==

[5] Group dialog is broken now [http://sourceforge.net/tracker/index.php?func=detail&aid=1796833&group_id=144022&atid=757416 bug 1796833]. So we should get old features work right before making new one. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)

== import/export .swf files ==

very important productivity feature

== import/export .svg frames sequence, and/or .svg animations ==

very important productivity feature

== a realtime .sif synchronized text window ==

just like the xml editor of Inkscape, or the html editor in Dreamweaver (this is hugelly useful for productivity)

I thinks scripting API can be implement in this way. For example you make XML DOM like implementation for python which alows to change DOM tree from python code and see chenges in canvas. By this way you can implement import/export scripts. Automation scripts. And a lot of different things. Even synchronization of animation between blender and synfig. --[[User:AkhIL|AkhIL]] 23:10, 26 April 2008 (EDT)

== choosing colour from gimp/inkscape palettes ==

very useful when you need some colour comformity of what you're doing

== Good high-level documentation of the source code ==

(2) It'd be nice if a newbie could quickly navigate around the source code. The best thing to do would be to add top-level comments in each file, explaining what that file does, a README.TXT in each directory, explaining what's in that directory. This would be pretty fast and easy to do, and make it much easier for new programmers to join.

Time permitting, it would also be good to document on a high level what the data structures are, but that's harder, since those tend to evolve, and it is often difficult to keep in sync. It would also be useful to document what individual functions do (just a one-liner high-level description), but that also takes more time.
: There is a page link in the wiki that connect to the [http://www.synfig.com/doc Synfig API Documentation]. I think this link should be highlighted to be more accessible for newbies contributors and mature developers (the link was found [[Releases/DeveloperPreview#Support | here]]). --[[User:Genete|Genete]] 10:02, 11 December 2007 (EST)

== Mathematical functions to animate ==
(2/4) If you want to make a waving flag, it would be handful a sine function, tuned with random correctors, for example.
: -This should generate waypoints each 1, 2, 4 frames or any other step at artist's wish.
: -When applying a function you can add it to current values, add it to 1st frame values or simply override old values. Perhaps other options (such multiplication) would be fine, too. Something like texture editor in [http://www.artofillusion.org Art of Illusion], perhaps.
Perhaps it would be useful reusing the [http://www.gnu.org/software/octave/ Octave] source code to parse mathematical expressions.
I have rated this wish with a '2' because undoubtly many users will not be familiar to mathematical concepts, but for those who will be, I'd rate it with a 4. It would be possible to make a ball describing a parabolic moving in no time.
[[User:ajotatxe|ajotatxe]] 20 November 2007
: dooglus can probably chime in better than I here (see his example of balls on mathematical paths at http://uk.youtube.com/watch?v=YTpSfUthuVE ), but I believe that this is already possible. Synfig does support a variety of mathematical transforms for parameters, although the way you do this is by no means intuitive. (You might also want to check out the preambletaffy.sifz example for an easier approach to a waving flag. I know you were just using that as an example, but for the record...) [[User:Pxegeek|Pxegeek]] 00:58, 21 November 2007 (EST)

: I'd also rate it with a (4) (and updated the rating accordingly), not for this special case, but to make many workarounds much easier. Simulating [Parabolic Shot|free fall], for example, would be a lot easier with real formulas. I don't know, though how easy it will be to implement, maybe waiting for a scripting interface to be implemented is better than hacking this feature in an ad-hoc manner. --[[User:Rubikcube|Rubikcube]] 16:38, 29 February 2008 (EST)

== Warning about editing bizarre things in animate editing mode ==
(3.5) It seems to have little sense animate certain things like Blend Method or Type of Feather. It would be very nice that the program asked comfirmation if you change these attributes in animate editing mode. If you do want to, you would have three options: "Yes, never ask", "Yes, never ask for this attribute", "No". I guess that internally, this attributes has integer type (or something like that) and the attributes that you normally want to animate, float type, so I think that this feature is relatively easy to implement. My English is not very good, so please feel free to fix this post.
[[User:ajotatxe|ajotatxe]] 20 November 2007

== Bones with FK & IK + grouping of objects into folders ==

(5) Bones cane move specific vector assigned to them or the bones can have envelopes that move the vectors within their field of influence, much Like Anime Studio/Moho does. It's quite a time saving process of animating. Objects created can be saved into separate groups or folders using the same system as Anime Studio/Moho -Shadowphoenix 27/8/2007

== Animated sketch ==

(5) it would be great, if the tool Sketch was animatable (for example, in a form of a special sketch-layer). --Zelgadis 2007-06-14

: For now as a workaround we could use animation program called Pencil. See [[Related Projects]] page. --[[User:Zelgadis|Zelgadis]]

: So, currently it could be achieved by using other software, but integration with synfig is poor, cause it requires importing a movie through a sequence of images. This is not intuitive and not obvious for new users. It will be good if synfig will have it implemented like [url=http://www.blender.org/development/release-logs/blender-248/grease-pencil/]blender's Grease Pencil[/url]. This feature will improve workflow, make synfig usable for frame-by frame animation (it is intuitive way of learning animation and powerful tool for producing preproduction work like animatic). --[[User:Zelgadis|Zelgadis]]

: It would be nice to also implement the onion peel feature, where you can see the frame before or after, and/or selectable keyframes if this is included. An example can be seen in the program Pencil--[[User:richardwad1|richardwad1]]

== Duck for Amount value in Zoom layer ==

(2) It would be nice if Amount value in Zoom layer was controlled by additional duck. --[[User:Zelgadis|Zelgadis]] 02:49, 29 December 2007 (EST)
: I found that I can better use Warp layer instead of Zoom to change size. But it'd be nice to have Amount duck for Zoom layer anyway...
:: The Amount parameter works exponentially; each time you add 1 to the Amount, the image is zoomed by a further factor of e (= 2.71828 or so). Would a duck be any use if it just controlled the value of Amount in a linear way?
:: Workarounds include: export Amount, select it in the children dialog. Whatever's selected in the children dialog shows a duck. You can adjust it using that duck.
:: Also, if you use a Stretch layer, convert the Amount to Composite, export the X-Axis and connect it to the Y-Axis, then you have a duck-controllable fixed-aspect zoom. -- [[User:Dooglus|dooglus]] 15:32, 15 January 2008 (EST)
::: Yeah I found this workaround, but it's to much actions - i prefer better use Warp or Stretch layers. Why not the link Amount duck and Amount value with logarithmic function? ;) --[[User:Zelgadis|Zelgadis]] 10:33, 17 January 2008 (EST)
::::[[Convert#Logarithm|Logarithm]] convert type for real parameters exists since svn 2034. [[User:Genete|Genete]] 10:17, 30 August 2008 (EDT)

== Automatic colour palette optimisation ==

(0) it would be nice to use libcontrast [http://david.navi.cx/blog/?p=132] [http://david.navi.cx/blog/?p=94] [http://david.navi.cx/blog/?p=99] [http://svn.gnome.org/svn/xchat-gnome/trunk/src/libcontrast/] to automatically adjust selected or all the palette items for best visual contrast. It would also be interesting to have a layer that uses this code to filter the image.

== Arbitrary Color Channels ==

— The ability for the user to create any number of custom channels for various purposes.

== Autorecover History ==

— It would be great if autorecover could also recover the associated history of a file in the event of a crash.

== Layer Convert ==

<strike>(4)</strike> (2) — The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''

== Vector fill bucket ==

(3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[Region Layer|region layer]]). Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

*Inkscape has a very innvative version of this tool. Maybe you can just grab the code from there and integrate it in synfig? --[[User:SvH|SvH]] 01:37, 14 May 2008 (EDT)

== [[redraw tool]] ==

(4-5) — Intutive reshaping of path-based layers. See link.

== [http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance] ==

— This should solve all complaints about the layout, without requiring Synfig to be "just like program (x)". See [[UI Reloaded]] for progress on this.

== Feedback for [[Smooth Move Tool]] ==

(3) — This tool does what a lot of folks are looking for, warping selected ducks in a "soft" fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an "influence gradient" overlaid on the canvas once Synfig's core is sped up?

== Networkability ==

(2) — Like Inkscape's "inkboard" feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option. This should probably farm off all the networking stuff to the telepathy framework so that synfig doesn't have to deal with all the account/etc issues.

== Intuitive tangent modification ==

(3) — (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.

-Agreed; blender does this with its IPO curves, and it's a really efficient way to work.

== Plugin API ==

(1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)

== Python support ==

(1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

I suppose to join this request with [[Wish_list#a_realtime_.sif_synchronized_text_window]]. We can implement python access to XML DOM and write XML Editor in python. --[[User:AkhIL|AkhIL]] 06:54, 30 April 2008 (EDT)

== mod_synfig ==

(1) — For Apache. Render .sif to some format like png/mng on access.

== synfig nsplugin ==

(1) — Let Mozilla and Mozilla-based view synfig files in-browser.

== Align function ==

(3) — Align objects at a common border (as in Inkscape)

== Improved SVG import ==

(4) — Currently, all importing an SVG does is render it in ImageMagick. What I want is the ability to import the SVG document so that all the shapes, etc. of the SVG document show up as their equivilant synfig layers - i.e. if I had put them there myself. I'm trying to write a patch for this but the codebase is mostly undocumented. [[User:KMeist|KMeist]] 16:38, 25 Feb 2006 (PST)

[[svg2synfig]] could be incorporated using an open source XSLT processor. --[[User:Dmd|Dmd]] 13:34, 26 January 2008 (EST)

== Gradient Paint Tool ==

How about a tool that can 'paint' a gradient object. For example the options would be width and gradient type, one would make a stroke with the tool and the gradient would be automatically applied inside of the outline (set by width). This would save the trouble of having to the all the encapsulation stuff. (Actually any tool that makes creating gradient one step would be good).--[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)

== Bone Animation Tools ==

Bone system with inverse kinematics, very important for quick animation. You put bones on a drawed man and you can animate him like a puppet. I'm using that in Moho (lost marble product).--[[User:Ziolive|ziolive]] 23 Aug 2006
*I would find this very useful too. I think it is called '''rigging'''(4/5) --[[User:SvH|SvH]] 01:33, 14 May 2008 (EDT)

== AVI Backgrounds ==
Is there any way I can add an avi as a background so I could add facial expressions to a stop-motion animated figure. [zotz here, I was thinking DV background or extra timeline. I would like to mix animations with live footage. rating (3/4)]
: Already implemented for ffmpeg pipeline of ppm in svn r2161 [[User:Genete|Genete]] 05:36, 9 November 2008 (EST)

== Character tool on Tool Options Dialog ==

I want to use the as a character generator for a TV show. By using chroma key hide the background. Even better interface to a video overlay card with Alpha blending.

== Collect for Publication ==

(3/4) - (zotz) Menu item, functionality that would collect alll files referenced in a sif and place them all in a tgz for sending elsewhere or publishing animations in source form.

== Object Library ==

(3/4) - (zotz) Haven't thought this all through yet, but synfig could come with a library of categotrised "objects" with a copyleft license (GPL? CC BY-SA?) An animation clip art type deal.
:I'd suggest this should be public domain and distributed by openclipart.org -- --[[User:PaulWise|pabs]]

== Flash Export ==

(3/4) Well, might just be me but if there was a posiblity to export in .swf or .fla, I think the project might become a lot more popular.[[User:Conceit|Conceit]]

(4/5) I wholeheartedly agree. I would definitely use synfig more if this feature were added and it would most definitely increase popularity. [[User:cdj05a|cdj05a]]

(4[me]/5[others]) Definitely would love flash export. There is no well maintained Flash animation studio that is Open Source. To have Synfig become that along with all that it already is would be absolutely wonderful. You'd also possibly add to your user base all the flash animators out there that don't want to pay Adobe. Some people would only want it for the flash animation hence the 5 for others. [[User:jblandrum|jblandrum]]

== Single window ==

Depending on individual desktop setups, single window is sometimes preferable to many windows. Can we have a single-window option?

Also, even with many windows, Windows-users especially might find it better if all the windows only appeared as a single one on the taskbar.

== Export Wizard ==

(2/4) Conversion and export to other file formats (mpg, avi, flash formats, others, and the synfig format) with a step by step wizard for choosing format and place of saving. Similar to Gimp's saving of .png files but for movie/video type files. --
[[User:Hiddenghost|hiddenghost]]

== Using Synfig as a portable app ==

(3) This isn't really a feature request (though it could be) but I was wondering if synfig could be used as a portable application (as in www.portableapps.com). Does the windows install require registry access? i really want to use Synfig at work, but I'm reluctant to install it just in case it leave footprints in the regisitry or something, and it would be sweet to use it on my travels as well. Only thing is, I can't test it out at home because I am using Linux.
See also: http://portableapps.com/node/5761
[[User:Zenoscope|zenoscope]]

This isn't currently possible without modifying the source code. That has been on my TODO list for ages [[User:PaulWise|pabs]] 01:17, 26 October 2007 (EDT)

== Allow organize child valuenodes in an hierarchy ==
(3-2) And allow maintain the organization once the file is saved. At the moment they are reordered in alphabetical order which is useless and annoying.

== Triangle sliders to be always visible ==
(3) I would like that the triangle sliders from [[Colors Dialog]] and [[Gradient Editor Dialog]] were visible whatever color or channel you're editing. Some times when the color or channel is to bright or light the slider is difficult to distinguish. --[[User:Genete|Genete]] 14:30, 29 October 2007 (EDT)

== XICC support ==

It would be cool if synfigstudio had support for [http://burtonini.com/blog/computers/xicc XICC].

== Area to Edit ==

An option like blender - select area to update would be nice, so the only part of the image that updates when you add or change something is in the selected area

ie. when working on a complex composition, studio doesn't know, when I tweak a tiny part of the composition, that only that part needs redrawing, so it redraws the whole thing. It would be good if there was some way of telling it which part to focus on. -- [[User:Dooglus|dooglus]] 04:02, 3 February 2008 (EST)

== Histograms ==

01:23 * AkhIL wish to have histograms and luma/color scope like [http://mac.softpedia.com/progScreenshots/Avid-Xpress-DV-Screenshot-14207.html] in synfig

I've looked at those pictures but don't know what they're showing. Can you describe what those scopes are doing, and what the histograms display? ie. what are the X and Y axes of the histograms? -- [[User:Dooglus|dooglus]] 04:07, 3 February 2008 (EST)

First look this description in blender wiki [http://wiki.blender.org/index.php/Manual/VSE_Modes]

Ok There is four things.
* Upper left is Lumascope (Luma Waveform in blender). X-Axis represents image's X-Axys. Y-Axis is average luminescence of column of pixels.
* Upper right is Chromascope (Chroma Vectorscope in blender). Just look description on blender wiki.
* Lower left is like Lumascope but for each channel
* Lower right is histograms. X is luminescence and Y is count of pixels with such luminiscence.

== Sound Layer ==

(4) It would be a very good improvement if the sound system were implemented into synfig in [[Sound Layer | this]] way. --[[User:Genete|Genete]] 07:46, 8 February 2008 (EST)

== Rearrange the view of waypoints for Canvas param ==
As reported in [http://sourceforge.net/tracker/index.php?func=detail&aid=1888858&group_id=144022&atid=757416 Bug #1888858] waypoints are not displayed for canvas switch events.
I suggest to rearrange waypoints display according to [[Media:Canvas_prop.png|this scheme]].

== Width weigths ==
Is it possible to add "weigths" for widths? ^_^ I.e. width changes not all the way along the segment. Maybe something like a duck on bline which indicates the region where the width of current vertex isn't changed.
[[Media:width-proposal.png|Illustration here.]]

More ideas around this concept in [http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-04-16.log this conversation]. Although the log of that day is very interesting the lines related to this idea are from 22:38 to 23:43. [[User:Genete|Genete]] 17:51, 16 April 2008 (EDT)

== Improved Colour Dialog ==
How easy is it to stick in a colour square/wheel? Messing with sliders is somewhat obstructive.

== Insert Waypoints ==
A button to create a waypoint for every selected duck, in its current position. Moving each duck up a bit and down again quickly gets tedious.
:If the duck in question has already a waypoint then you don't need to move it to create a new waypoint. Just select the corresponding parameter in your child list panel and select 'Add Waypoint' from the right click context menu over the parameter. No need to have the duck selected. If you want to freeze the entire bline just do that over the Bline Point List. [[User:Genete|Genete]] 07:48, 29 April 2008 (EDT)
::Yes, but it would be nice to have opportunity to add waypoint to parameer which not have any ducks yet (i.e. non-animated parameter). --[[User:Zelgadis|Zelgadis]] 08:33, 29 April 2008 (EDT)

== Automatically split tangeants ==

Holding shift while moving tangeant ducks should automatically split them. They can be rejoined if necessary through the context menu as they are now.

== A way to link params without exporting ==
I need a way to link params with different names without exporting. It is possible to achive by manualy editing of sif file. But inposible by gui. I will be nice to have linking by drag-n-drop. Or just by selecting reference param, pushing copy button, selecting another param and bushing link button. ---[[User:AkhIL|AkhIL]] 21:47, 30 May 2008 (EDT)

== Allow select the origin of rotation when using the Rotate Tool ==

It can be initially set to the geometrical center of the selected ducks or the gravity center depending of the selected checkboxes in the tool options panel. Later the user could move it before perform the rotation operation. It is a waste of time to rotate and translate the ducks every time a rotation manipulation is done. ---[[User:Genete|Genete]] 12:16, 4 June 2008 (EDT)

:I was adding this request at the same time than you Genete :-). Here is an example of how this issue is solved in Inkscape:

:[[Image:rotate-tool-inkscape.png|center]]

:---[[User:Yaco|Yaco]]

== Labels for rows in the Timetrack window [1]==
The rows in the timetrack palette and the parameters palette are obviously related, doing a scroll in the Timetrack window with the mouse makes the parameters window scroll.

It's be nice to have the rows labeled with the corresponding label from the parameters palette, and to have the "list" parameter at the top of the time track window, with the possibility of dragging them around to move them up or down, personally I would prefer the "list" to be up the top so I can see the keyframes I'm making.

[[Image:Stencil 3.jpg|center]]

:Is this what you want? Just arrange the dock able dialogs as you need. [[User:Genete|Genete]] 10:03, 30 July 2008 (EDT)

:[[Image:Params-TimeTrack.png]]

:---[[User:zenoscope|zenoscope]]

== Non-symetrical but "smooth" tangents on ducks ==
Add another mode for duck tangent, where the tangent can have different radius, but keep the same angle. (a "split tangents (radius only)" mode).

== Dockable windows ==
seriously the current GUI is wasting space by showing the background desktop and it's showing 5 tabs instead of one tab (windows version)

:--[[User:super animator|super animator]]

== Combining the installations files ==
Seriously, there should be one installation file not four. This is probably one of the reasons why not very much people use this program, because they only get one installation file from other websites and they probably are having a hard time running the program and getting frustrated.

:--[[User:super animator|super animator]]

== A Particle Tool/Particle Object Editor ==
I thought it might be interesting to add a Particle tool that is intuitive. Genete's script is amazing and I am sure I will do a lot of things with it once I have a chance to sit down and figure it out, but if there were a way to make it into tool with all the settings on sliders, it would be much easier. His script adds endless possibilities of nice effects to make animations look better. I personally rate this rather high. 3.5/5

:--[[User:richardwad1|richardwad1]]

== A programation language as code behind like python, ruby or any ==
Code behind should be important to program the animation or events associated, programers and designers could work in a colaborative workspace and make applications with richfull content on desktop applicactions or web applications like expression blend or macromedia flash CS.

:--[[User:nickholai|nickholai]]

== Embedding animation on web applications ==
Like Macromedia Flash, it seems to require a plug in for internet explorer or firefox diferent as silverlight or flash, open source and "software libre" projects are working on animation but using the flash plug in, this wish needs a free plug in.

:--[[User:nickholai|nickholai]]

Dev:Mingw installation

2009-01-09T16:53:26Z

Creek23: /* [http://www.gnu.org/software/gettext Gettext] */ re-worded

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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]===
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]===
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:

* libsigc++
* cairomm
* glibmm
* gtkmm
* libxml++

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.

Dev:Mingw installation

2009-01-09T16:51:38Z

Creek23: /* [http://www.gnu.org/software/gettext Gettext] */ update/note

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 compile-free problem.

'''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]===
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]===
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:

* libsigc++
* cairomm
* glibmm
* gtkmm
* libxml++

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.

Dev:Mingw installation

2009-01-09T16:50:12Z

Creek23: /* [http://www.gnu.org/software/gettext Gettext] */ added GetText-Devel for MSYS

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 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.

# 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 compile-free problem.

===[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]===
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]===
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:

* libsigc++
* cairomm
* glibmm
* gtkmm
* libxml++

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.

Dev:Mingw installation

2009-01-09T15:38:26Z

Creek23: /* [http://www.gnu.org/software/libtool/ libtool] */

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 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]===
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]===
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:

* libsigc++
* cairomm
* glibmm
* gtkmm
* libxml++

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.

Dev:Mingw installation

2009-01-09T15:38:03Z

Creek23: /* [http://www.gnu.org/software/automake/ automake] */ hilighted

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 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]===
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]===
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:

* libsigc++
* cairomm
* glibmm
* gtkmm
* libxml++

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.

Dev:Mingw installation

2009-01-09T15:37:25Z

Creek23: /* [http://www.gnu.org/software/autoconf/ autoconf] */ hilighted

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 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]===
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]===
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:

* libsigc++
* cairomm
* glibmm
* gtkmm
* libxml++

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.

Dev:Building on Windows

2009-01-08T22:35:21Z

Creek23: /* _filez directory */ mark of deletion for patching

[[Category:Building]]

==Directories==
If you didn't already install Mingw, [[Mingw installation|this page]] will guide you through the process.

If you didn't already start an msys session, do so now. Just double click the MSYS shortcut or run <code>'''C:\msys\1.0\msys.bat'''</code>. An msys session will be opened, creating your profile directory at <code>'''C:\msys\1.0\home\<windows login>'''</code>. As you can see, MinGW uses your windows login as the user name in its fake UNIX environment. Be careful, I've not checked whether it works with non latin-character account names.

Now, use explorer or your favorite file manager and go to <code>'''C:\msys\1.0\home\<windows login>'''</code>. Create a directory there for all Synfig operations. For example, let it be <code>'''synfig'''</code>. Go into this directory.

Ok, now you are at <code>'''C:\msys\1.0\home\<windows login>\synfig'''</code>. Create four directories here:
* <code>'''_filez'''</code>, for patches (and maybe later, additional files).
* <code>'''_src'''</code>, for program sources.
* <code>'''build'''</code>, for building programs.
* <code>'''temp'''</code>, for local installation programs and libraries, which are required for building synfig. (For example: ETL, synfig (core for studio), OpenEXR, etc...)

Of course, you can choose your own name for all the directories and choose their locations. All you need then is to set a new path in the configuration file. But for now we choose the easy way.

==Files==
Save this configuration file as <code>C:\msys\1.0\home\<windows login>\synfig\synbuild.conf</code>:

<code><pre><nowiki>
# Synfig for Win32 build configuration script.
#############################################################################
# 1. Files and Directories

# Uncompressed Synfig svn snapshots and another package sources
SYN_SOURCE_DIR=`dirname ~/.`"/synfig/_src"

# Directory additional files (patches f.e.)
SYN_FILEZ_DIR=`dirname ~/.`"/synfig/_filez"

# Temporary installations (ETL headers, synfig binaries for icon and image making)
SYN_TEMP_INSTALL=`dirname ~/.`"/synfig/temp"

# Build directory
SYN_BUILD_DIR=`dirname ~/.`"/synfig/build"

# OpenEXR source package
SYN_ILMBASE_VERSION="1.0.1"
SYN_ILMBASE_SRC="${SYN_SOURCE_DIR}/ilmbase-${SYN_ILMBASE_VERSION}.tar.gz"
SYN_OPENEXR_VERSION="1.6.1"
SYN_OPENEXR_SRC="${SYN_SOURCE_DIR}/openexr-${SYN_OPENEXR_VERSION}.tar.gz"

#############################################################################
# 2. External tools

# Path to ImageMagick directory.
SYN_IMAGEMAGICK_PATH="/C/Program Files/ImageMagick"

# Path to Subversion bin directory.
SYN_SUBVERSION_PATH="/C/Program Files/Subversion/bin"

# Path to NSIS directory with makensis.exe file.
SYN_NSIS_PATH="/C/Program Files/NSIS"

#############################################################################
# 3. Build setup

# Build host
MINGW_HOST="mingw32"

# Make debug build of Synfig Core
SYN_CORE_DEBUG_BUILD="no"

# Make debug build of Synfig Studio
SYN_STUDIO_DEBUG_BUILD="no"
#WITH_FMOD="yes"

#############################################################################
# 4. Patches (you can place here any additional patches)

# ETL patches
ETL_PATCHES=$(cat <<:END_ETL:
:END_ETL:)

# Synfig Core patches
SYNCORE_PATCHES=$(cat <<:END_SYNCORE:
:END_SYNCORE:)

# Sunfig Studio patches
SYNSTUDIO_PATCHES=$(cat <<:END_SYNSTUDIO:
:END_SYNSTUDIO:)

# OpenEXR ILMBase patches

ILMBASE_PATCHES=$(cat <<:END_ILMBASE:
ilmbase-1.0.1-makefile.patch
ilmbase-1.0.1-pkgconfig.patch
:END_ILMBASE:)

# OpenEXR patches
#openexr-1.4.0-pkgconfig.patch
#openexr-1.4.0-mingw32.patch
OPENEXR_PATCHES=$(cat <<:END_OPENEXR:
:END_OPENEXR:)

#############################################################################
# 5. Autoconfiguration

if [ "$GTK_BASEPATH" ]; then
CPPFLAGS="-I${GTK_BASEPATH}/include $CPPFLAGS"
fi

if [ "$SYN_IMAGEMAGICK_PATH" ]; then
PATH="${SYN_IMAGEMAGICK_PATH}:${PATH}"
fi

if [ "$SYN_SUBVERSION_PATH" ]; then
PATH="${SYN_SUBVERSION_PATH}:${PATH}"
fi

if [ "$SYN_NSIS_PATH" ]; then
PATH="${SYN_NSIS_PATH}:${PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/ETL" ]; then
PATH="${SYN_TEMP_INSTALL}/ETL/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/ETL/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/synfig-devel" ]; then
PATH="${SYN_TEMP_INSTALL}/synfig-devel/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/openexr" ]; then
PATH="${SYN_TEMP_INSTALL}/openexr/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/openexr/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

export PATH
export PKG_CONFIG_PATH
export CPPFLAGS
</nowiki></pre></code>

Save OpenEXR build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_openexr.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making OpenEXR..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/ilmbase-${SYN_ILMBASE_VERSION}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/ilmbase
[ $? -eq 0 ] || exit 1

rm -rf ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/openexr
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
echo PATH is $PATH
echo tar -xzf ${SYN_ILMBASE_SRC} -C ${SYN_BUILD_DIR}
tar -xzf ${SYN_ILMBASE_SRC} -C ${SYN_BUILD_DIR}
[ $? -eq 0 ] || exit 1
echo tar -xzf ${SYN_OPENEXR_SRC} -C ${SYN_BUILD_DIR}
tar -xzf ${SYN_OPENEXR_SRC} -C ${SYN_BUILD_DIR}
[ $? -eq 0 ] || exit 1

echo "Applying patches for ILMBase... "
cd ${SYN_BUILD_DIR}/ilmbase-${SYN_ILMBASE_VERSION}
[ $? -eq 0 ] || exit 1
for SFILE in ${ILMBASE_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring ILMbase"
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/openexr \
--disable-static --disable-threading --disable-posix-sem
[ $? -eq 0 ] || exit 1

echo "Making"
make
[ $? -eq 0 ] || exit 1
make install
[ $? -eq 0 ] || exit 1
echo "ILMBase Done"

echo "Applying patches for OpenEXR... "
cd ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
[ $? -eq 0 ] || exit 1
for SFILE in ${OPENEXR_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

# Now the temp/openexr dir exists, we can add it to paths
if [ -d "${SYN_TEMP_INSTALL}/openexr" ]; then
PATH="${SYN_TEMP_INSTALL}/openexr/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/openexr/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

export PATH
export PKG_CONFIG_PATH

echo "Configuring OpenEXR"
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/openexr \
--disable-static --disable-threading --disable-posix-sem --disable-ilmbasetest
[ $? -eq 0 ] || exit 1

echo "separately build b44ExpLogTable as the openexr script doesn't work under msys"
cd ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}/IlmImf
[ $? -eq 0 ] || exit 1
mingw32-g++ --verbose -g -O2 -I${SYN_TEMP_INSTALL}/openexr/include/OpenEXR -L${SYN_TEMP_INSTALL}/openexr/lib b44ExpLogTable.cpp -lHalf -o b44ExpLogTable
[ $? -eq 0 ] || exit 1
cd ..
[ $? -eq 0 ] || exit 1

echo "Making"
make
[ $? -eq 0 ] || exit 1
make install
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
# rm -rf ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
# [ $? -eq 0 ] || exit 1

echo "Done: OpenEXR"
</nowiki></pre></code>

Save ETL build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_etl.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making ETL..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/ETL
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/ETL/* ${SYN_BUILD_DIR}/ETL/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/ETL/.svn ${SYN_BUILD_DIR}/ETL/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
for SFILE in ${ETL_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
autoreconf -if
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/ETL
[ $? -eq 0 ] || exit 1

echo "Making"
make install
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1

echo "Done: ETL"
</nowiki></pre></code>

Save Synfig Core build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_core.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making Synfig-Core..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/synfig-devel
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-core/* ${SYN_BUILD_DIR}/synfig-core/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-core/.svn ${SYN_BUILD_DIR}/synfig-core/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
for SFILE in ${SYNCORE_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
libtoolize --ltdl --copy -f
autoreconf -if
[ $? -eq 0 ] || exit 1
mkdir win32build
[ $? -eq 0 ] || exit 1
cd win32build
[ $? -eq 0 ] || exit 1
if [ "$SYN_CORE_DEBUG_BUILD" == "yes" ]; then
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --disable-optimization --enable-debug
[ $? -eq 0 ] || exit 1
else
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --enable-optimization=1 --disable-debug
[ $? -eq 0 ] || exit 1
fi

echo "Making"
# libtool hack patch [begin]
patch -p2 <${SYN_FILEZ_DIR}/synfig-core-hack-libtool.patch
[ $? -eq 0 ] || exit 1
# libtool hack patch [end]
make package
[ $? -eq 0 ] || exit 1
mv ./synfig-*.exe ${CURRENT_DIR}/
[ $? -eq 0 ] || exit 1

make clean
[ $? -eq 0 ] || exit 1
# auto build hack installation [begin]
make install prefix=${SYN_TEMP_INSTALL}/synfig-devel
[ $? -eq 0 ] || exit 1
# auto build hack installation [end]
cd ${CURRENT_DIR}

# auto build hack patch [begin]
echo "Postprocessing"
SYN_SED_PATH=`echo ${SYN_TEMP_INSTALL}/synfig-devel | sed -e 's/\//\\\\\//g'`
[ $? -eq 0 ] || exit 1
mv ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp
[ $? -eq 0 ] || exit 1
sed -e "s/C:\/PROGRA~1\\/Synfig/${SYN_SED_PATH}/g" \
${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp >${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config
[ $? -eq 0 ] || exit 1
rm -f ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp
[ $? -eq 0 ] || exit 1
mv ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp
[ $? -eq 0 ] || exit 1
sed -e "s/C:\/PROGRA~1\\/Synfig/${SYN_SED_PATH}/g" \
${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp >${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc
[ $? -eq 0 ] || exit 1
rm -f ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp
[ $? -eq 0 ] || exit 1
# auto build hack patch [end]

rm -rf ${SYN_BUILD_DIR}/synfig-core

echo "Done: synfig-core"
</nowiki></pre></code>

Save Synfig Studio build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_studio.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making Synfig-Studio..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-studio/* ${SYN_BUILD_DIR}/synfig-studio/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-studio/.svn ${SYN_BUILD_DIR}/synfig-studio/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1
for SFILE in ${SYNSTUDIO_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
autoreconf -if
[ $? -eq 0 ] || exit 1
mkdir win32build
[ $? -eq 0 ] || exit 1
cd win32build
[ $? -eq 0 ] || exit 1
if [ "$SYN_STUDIO_DEBUG_BUILD" == "yes" ]; then
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --disable-optimization --enable-debug
[ $? -eq 0 ] || exit 1
else
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --enable-optimization=1 --disable-debug
[ $? -eq 0 ] || exit 1
fi

echo "Making"
make package
[ $? -eq 0 ] || exit 1

mv ./synfigstudio-*.exe ${CURRENT_DIR}/
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1

echo "Done: synfig-studio"
</nowiki></pre></code>

===_src directory===
Go to the <code>C:\msys\1.0\home\<windows login>\synfig\_src</code> directory. Get the latest sources of Synfig from its repository.

:: <code>'''$ svn co <nowiki>https://synfig.svn.sourceforge.net/svnroot/synfig/ETL/trunk/ </nowiki> ETL'''</code> 
:: <code>'''$ svn co <nowiki>https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-core/trunk/ </nowiki> synfig-core'''</code> 
:: <code>'''$ svn co <nowiki>https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-studio/trunk/ </nowiki> synfig-studio'''</code> 

'''Note:''' The commands have a space between the URL address and the third paramater, it's easy to miss it. There should be three, space separated, paramaters in total after the "'''svn'''" command.

Download the current stable [http://www.openexr.com/ OpenEXR] version from:

* http://download.savannah.gnu.org/releases-noredirect/openexr/ilmbase-1.0.1.tar.gz (452 KB)
* http://download.savannah.gnu.org/releases-noredirect/openexr/openexr-1.6.1.tar.gz (13 MB)

Finally, you must have three directories (ETL, synfig-core and synfig-studio) and the ilmbase-1.0.1.tar.gz & openexr-1.6.1.tar.gz files in your <code>'''_src'''</code> directory.

===_filez directory===
Save the following text as <code>'''C:\msys\1.0\home\<windows login>\synfig\_filez\synfig-core-hack-libtool.patch'''</code>:
<code><pre><nowiki>
diff -Nuar synfig-core.orig/win32build/libtool synfig-core/win32build/libtool
--- synfig-core.orig/win32build/libtool Wed Feb 7 21:52:34 2007
+++ synfig-core/win32build/libtool Wed Feb 7 21:57:12 2007
@@ -2805,7 +2805,7 @@
fi
elif test "$build_libtool_libs" = yes; then
# Not a shared library
- if test "$deplibs_check_method" != pass_all; then
+ if test "$deplibs_check_method" != pass_all && test "$old_library" != "libltdl.a"; then
# We're trying link a shared library against a static one
# but the system doesn't support it.

</nowiki></pre></code>

Then save the following as <code>'''C:\msys\1.0\home\<windows login>\synfig\_filez\ilmbase-1.0.1-makefile.patch'''</code>:
<code><pre><nowiki>
diff -Nuar ilmbase-1.0.1.orig/IlmThread/Makefile.in ilmbase-1.0.1/IlmThread/Makefile.in
--- ilmbase-1.0.1.orig/IlmThread/Makefile.in Tue Oct 9 14:28:29 2007
+++ ilmbase-1.0.1/IlmThread/Makefile.in Sat Aug 16 18:35:08 2008
@@ -64,7 +64,8 @@
am_libIlmThread_la_OBJECTS = IlmThreadPool.lo IlmThread.lo \
IlmThreadSemaphore.lo IlmThreadMutex.lo IlmThreadPosix.lo \
IlmThreadSemaphorePosix.lo IlmThreadSemaphorePosixCompat.lo \
- IlmThreadMutexPosix.lo
+ IlmThreadMutexPosix.lo IlmThreadWin32.lo IlmThreadSemaphoreWin32.lo \
+ IlmThreadMutexWin32.lo
libIlmThread_la_OBJECTS = $(am_libIlmThread_la_OBJECTS)
DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir)/config
depcomp = $(SHELL) $(top_srcdir)/depcomp
</nowiki></pre></code>

Finally save the following as <code>'''C:\msys\1.0\home\<windows login>\synfig\_filez\ilmbase-1.0.1-pkgconfig.patch'''</code>:
<code><pre><nowiki>
diff -Nuar ilmbase-1.0.1.orig/IlmBase.pc.in ilmbase-1.0.1/IlmBase.pc.in
--- ilmbase-1.0.1.orig/IlmBase.pc.in Wed Dec 13 14:55:53 2006
+++ ilmbase-1.0.1/IlmBase.pc.in Sat Aug 16 21:06:27 2008
@@ -7,5 +7,5 @@
Name: IlmBase
Description: Base math and exception libraries
Version: @ILMBASE_VERSION@
-Libs: -L${libdir} -lImath -lHalf -lIex -lIlmThread @PTHREAD_LIBS@
-Cflags: @PTHREAD_CFLAGS@ -I${OpenEXR_includedir}
+Libs: -L${libdir} -lImath -lHalf -lIex -lIlmThread
+Cflags: -I@includedir@ -I${OpenEXR_includedir}
</nowiki></pre></code>

<s>Last but not least, prior to SVN 2055, the Windows installer files need patching - http://patches.synfig.org/r/3/</s> -- ''(it's been done)''.

(Acknowledgment to the writer of http://qtpfsgui.wiki.sourceforge.net/Compiling+on+Windows for the tip on the b44ExpLogTable file in OpenEXR)

==Configuration==
This section describes the parameters of <code>synbuild.conf</code> file.

===Files and Directories===
As you can see in this section you can define the path and name of the special directories (with sources, patches and temporary directories). If you install the build scripts as written above, there is nothing to change.

Also this section contains the path and version of the OpenEXR source files.

===External tools===
In this section you need to define the path to the executable files of the three auxiliary packages: ImageMagick, Subversion and NSIS. ImageMagick and Subversion binaries are located using the PATH environment variable, but their paths are added to the end of the path list and so we can get name collisions. For example, the ImageMagick "convert" tool has the same name as the "convert" tool from Borland Delphi Explorer, which may have been installed before ImageMagick.

===Build setup===
'''MINGW_HOST''' - host parameter of "configure" script. Do not change it.

'''SYN_CORE_DEBUG_BUILD''' - if "yes", Synfig Core will be made with debug info.

'''SYN_STUDIO_DEBUG_BUILD''' - if "yes", Synfig Studio will be made with debug info.

===Patches===
In this section you can find a number of patch definition blocks, looking like this:

<table style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"><tr><td>
<pre># ETL patches
ETL_PATCHES=$(cat <<:END_ETL:
:END_ETL:)</pre></td></tr></table>

For example, if you place any filenames of patches between '':END_ETL:'' blocks, it will be applied before the configuration of ETL. Patch files need to be stored in the <code>_filez</code> directory.

This section is useful if you want to test your own patches before sending them to the Synfig developers.

===Autoconfiguration===
This section contatins code which sets up the required environment variables and (by default) there is no need to change anything.

==Build Order==
Note: If you want build synfig without slowing down other tasks running on the same machine while the build takes place, open a single msys session, then open "Task Manager", search for the ''sh.exe'' process and set its priority to "Below normal".

Note: Running an on-access antivirus scanner can dramatically decrease compilation speed.

===OpenEXR===
This package needs to be built only once. A rebuild is only required if you get a new version or want to apply a new patch to it or you update the compiler and it is incompatible with the previous binaries.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_openexr.sh</nowiki></blockquote>

Wait for the "Done: OpenEXR" message.

===ETL===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_etl.sh</nowiki></blockquote>

Wait for the "Done: ETL" message.

===Synfig Core===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_core.sh</nowiki></blockquote>

Wait for the "Done: synfig-core" message. It can take a long time. The Synfig Core installer will be moved into the current directory.

===Synfig Studio===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_studio.sh</nowiki></blockquote>

Wait for the "Done: synfig-studio" message. It can take a long time. The Synfig Studio installer will be moved into the current directory.

==Additional tools==
These tools are not required to build Synfig, but they can help in the debugging process.

P.S. Post this later. ;-)

(Atrus - keen to hear what you recommend for debug. Also any debug processes you go through to fix the bugs. There's several bugs (mainly preview rendering) that I see under the current builds of Windows that are not under Linux or the old 0.61.05 for Windows - Pxegeek 2/7/07)

[[Category:Windows]]

Dev:Building on Windows

2009-01-08T22:25:57Z

Creek23: /* _src directory */ changed OpenEXR and ILMBase link

[[Category:Building]]

==Directories==
If you didn't already install Mingw, [[Mingw installation|this page]] will guide you through the process.

If you didn't already start an msys session, do so now. Just double click the MSYS shortcut or run <code>'''C:\msys\1.0\msys.bat'''</code>. An msys session will be opened, creating your profile directory at <code>'''C:\msys\1.0\home\<windows login>'''</code>. As you can see, MinGW uses your windows login as the user name in its fake UNIX environment. Be careful, I've not checked whether it works with non latin-character account names.

Now, use explorer or your favorite file manager and go to <code>'''C:\msys\1.0\home\<windows login>'''</code>. Create a directory there for all Synfig operations. For example, let it be <code>'''synfig'''</code>. Go into this directory.

Ok, now you are at <code>'''C:\msys\1.0\home\<windows login>\synfig'''</code>. Create four directories here:
* <code>'''_filez'''</code>, for patches (and maybe later, additional files).
* <code>'''_src'''</code>, for program sources.
* <code>'''build'''</code>, for building programs.
* <code>'''temp'''</code>, for local installation programs and libraries, which are required for building synfig. (For example: ETL, synfig (core for studio), OpenEXR, etc...)

Of course, you can choose your own name for all the directories and choose their locations. All you need then is to set a new path in the configuration file. But for now we choose the easy way.

==Files==
Save this configuration file as <code>C:\msys\1.0\home\<windows login>\synfig\synbuild.conf</code>:

<code><pre><nowiki>
# Synfig for Win32 build configuration script.
#############################################################################
# 1. Files and Directories

# Uncompressed Synfig svn snapshots and another package sources
SYN_SOURCE_DIR=`dirname ~/.`"/synfig/_src"

# Directory additional files (patches f.e.)
SYN_FILEZ_DIR=`dirname ~/.`"/synfig/_filez"

# Temporary installations (ETL headers, synfig binaries for icon and image making)
SYN_TEMP_INSTALL=`dirname ~/.`"/synfig/temp"

# Build directory
SYN_BUILD_DIR=`dirname ~/.`"/synfig/build"

# OpenEXR source package
SYN_ILMBASE_VERSION="1.0.1"
SYN_ILMBASE_SRC="${SYN_SOURCE_DIR}/ilmbase-${SYN_ILMBASE_VERSION}.tar.gz"
SYN_OPENEXR_VERSION="1.6.1"
SYN_OPENEXR_SRC="${SYN_SOURCE_DIR}/openexr-${SYN_OPENEXR_VERSION}.tar.gz"

#############################################################################
# 2. External tools

# Path to ImageMagick directory.
SYN_IMAGEMAGICK_PATH="/C/Program Files/ImageMagick"

# Path to Subversion bin directory.
SYN_SUBVERSION_PATH="/C/Program Files/Subversion/bin"

# Path to NSIS directory with makensis.exe file.
SYN_NSIS_PATH="/C/Program Files/NSIS"

#############################################################################
# 3. Build setup

# Build host
MINGW_HOST="mingw32"

# Make debug build of Synfig Core
SYN_CORE_DEBUG_BUILD="no"

# Make debug build of Synfig Studio
SYN_STUDIO_DEBUG_BUILD="no"
#WITH_FMOD="yes"

#############################################################################
# 4. Patches (you can place here any additional patches)

# ETL patches
ETL_PATCHES=$(cat <<:END_ETL:
:END_ETL:)

# Synfig Core patches
SYNCORE_PATCHES=$(cat <<:END_SYNCORE:
:END_SYNCORE:)

# Sunfig Studio patches
SYNSTUDIO_PATCHES=$(cat <<:END_SYNSTUDIO:
:END_SYNSTUDIO:)

# OpenEXR ILMBase patches

ILMBASE_PATCHES=$(cat <<:END_ILMBASE:
ilmbase-1.0.1-makefile.patch
ilmbase-1.0.1-pkgconfig.patch
:END_ILMBASE:)

# OpenEXR patches
#openexr-1.4.0-pkgconfig.patch
#openexr-1.4.0-mingw32.patch
OPENEXR_PATCHES=$(cat <<:END_OPENEXR:
:END_OPENEXR:)

#############################################################################
# 5. Autoconfiguration

if [ "$GTK_BASEPATH" ]; then
CPPFLAGS="-I${GTK_BASEPATH}/include $CPPFLAGS"
fi

if [ "$SYN_IMAGEMAGICK_PATH" ]; then
PATH="${SYN_IMAGEMAGICK_PATH}:${PATH}"
fi

if [ "$SYN_SUBVERSION_PATH" ]; then
PATH="${SYN_SUBVERSION_PATH}:${PATH}"
fi

if [ "$SYN_NSIS_PATH" ]; then
PATH="${SYN_NSIS_PATH}:${PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/ETL" ]; then
PATH="${SYN_TEMP_INSTALL}/ETL/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/ETL/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/synfig-devel" ]; then
PATH="${SYN_TEMP_INSTALL}/synfig-devel/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/openexr" ]; then
PATH="${SYN_TEMP_INSTALL}/openexr/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/openexr/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

export PATH
export PKG_CONFIG_PATH
export CPPFLAGS
</nowiki></pre></code>

Save OpenEXR build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_openexr.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making OpenEXR..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/ilmbase-${SYN_ILMBASE_VERSION}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/ilmbase
[ $? -eq 0 ] || exit 1

rm -rf ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/openexr
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
echo PATH is $PATH
echo tar -xzf ${SYN_ILMBASE_SRC} -C ${SYN_BUILD_DIR}
tar -xzf ${SYN_ILMBASE_SRC} -C ${SYN_BUILD_DIR}
[ $? -eq 0 ] || exit 1
echo tar -xzf ${SYN_OPENEXR_SRC} -C ${SYN_BUILD_DIR}
tar -xzf ${SYN_OPENEXR_SRC} -C ${SYN_BUILD_DIR}
[ $? -eq 0 ] || exit 1

echo "Applying patches for ILMBase... "
cd ${SYN_BUILD_DIR}/ilmbase-${SYN_ILMBASE_VERSION}
[ $? -eq 0 ] || exit 1
for SFILE in ${ILMBASE_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring ILMbase"
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/openexr \
--disable-static --disable-threading --disable-posix-sem
[ $? -eq 0 ] || exit 1

echo "Making"
make
[ $? -eq 0 ] || exit 1
make install
[ $? -eq 0 ] || exit 1
echo "ILMBase Done"

echo "Applying patches for OpenEXR... "
cd ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
[ $? -eq 0 ] || exit 1
for SFILE in ${OPENEXR_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

# Now the temp/openexr dir exists, we can add it to paths
if [ -d "${SYN_TEMP_INSTALL}/openexr" ]; then
PATH="${SYN_TEMP_INSTALL}/openexr/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/openexr/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

export PATH
export PKG_CONFIG_PATH

echo "Configuring OpenEXR"
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/openexr \
--disable-static --disable-threading --disable-posix-sem --disable-ilmbasetest
[ $? -eq 0 ] || exit 1

echo "separately build b44ExpLogTable as the openexr script doesn't work under msys"
cd ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}/IlmImf
[ $? -eq 0 ] || exit 1
mingw32-g++ --verbose -g -O2 -I${SYN_TEMP_INSTALL}/openexr/include/OpenEXR -L${SYN_TEMP_INSTALL}/openexr/lib b44ExpLogTable.cpp -lHalf -o b44ExpLogTable
[ $? -eq 0 ] || exit 1
cd ..
[ $? -eq 0 ] || exit 1

echo "Making"
make
[ $? -eq 0 ] || exit 1
make install
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
# rm -rf ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
# [ $? -eq 0 ] || exit 1

echo "Done: OpenEXR"
</nowiki></pre></code>

Save ETL build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_etl.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making ETL..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/ETL
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/ETL/* ${SYN_BUILD_DIR}/ETL/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/ETL/.svn ${SYN_BUILD_DIR}/ETL/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
for SFILE in ${ETL_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
autoreconf -if
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/ETL
[ $? -eq 0 ] || exit 1

echo "Making"
make install
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1

echo "Done: ETL"
</nowiki></pre></code>

Save Synfig Core build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_core.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making Synfig-Core..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/synfig-devel
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-core/* ${SYN_BUILD_DIR}/synfig-core/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-core/.svn ${SYN_BUILD_DIR}/synfig-core/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
for SFILE in ${SYNCORE_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
libtoolize --ltdl --copy -f
autoreconf -if
[ $? -eq 0 ] || exit 1
mkdir win32build
[ $? -eq 0 ] || exit 1
cd win32build
[ $? -eq 0 ] || exit 1
if [ "$SYN_CORE_DEBUG_BUILD" == "yes" ]; then
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --disable-optimization --enable-debug
[ $? -eq 0 ] || exit 1
else
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --enable-optimization=1 --disable-debug
[ $? -eq 0 ] || exit 1
fi

echo "Making"
# libtool hack patch [begin]
patch -p2 <${SYN_FILEZ_DIR}/synfig-core-hack-libtool.patch
[ $? -eq 0 ] || exit 1
# libtool hack patch [end]
make package
[ $? -eq 0 ] || exit 1
mv ./synfig-*.exe ${CURRENT_DIR}/
[ $? -eq 0 ] || exit 1

make clean
[ $? -eq 0 ] || exit 1
# auto build hack installation [begin]
make install prefix=${SYN_TEMP_INSTALL}/synfig-devel
[ $? -eq 0 ] || exit 1
# auto build hack installation [end]
cd ${CURRENT_DIR}

# auto build hack patch [begin]
echo "Postprocessing"
SYN_SED_PATH=`echo ${SYN_TEMP_INSTALL}/synfig-devel | sed -e 's/\//\\\\\//g'`
[ $? -eq 0 ] || exit 1
mv ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp
[ $? -eq 0 ] || exit 1
sed -e "s/C:\/PROGRA~1\\/Synfig/${SYN_SED_PATH}/g" \
${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp >${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config
[ $? -eq 0 ] || exit 1
rm -f ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp
[ $? -eq 0 ] || exit 1
mv ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp
[ $? -eq 0 ] || exit 1
sed -e "s/C:\/PROGRA~1\\/Synfig/${SYN_SED_PATH}/g" \
${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp >${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc
[ $? -eq 0 ] || exit 1
rm -f ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp
[ $? -eq 0 ] || exit 1
# auto build hack patch [end]

rm -rf ${SYN_BUILD_DIR}/synfig-core

echo "Done: synfig-core"
</nowiki></pre></code>

Save Synfig Studio build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_studio.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making Synfig-Studio..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-studio/* ${SYN_BUILD_DIR}/synfig-studio/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-studio/.svn ${SYN_BUILD_DIR}/synfig-studio/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1
for SFILE in ${SYNSTUDIO_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
autoreconf -if
[ $? -eq 0 ] || exit 1
mkdir win32build
[ $? -eq 0 ] || exit 1
cd win32build
[ $? -eq 0 ] || exit 1
if [ "$SYN_STUDIO_DEBUG_BUILD" == "yes" ]; then
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --disable-optimization --enable-debug
[ $? -eq 0 ] || exit 1
else
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --enable-optimization=1 --disable-debug
[ $? -eq 0 ] || exit 1
fi

echo "Making"
make package
[ $? -eq 0 ] || exit 1

mv ./synfigstudio-*.exe ${CURRENT_DIR}/
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1

echo "Done: synfig-studio"
</nowiki></pre></code>

===_src directory===
Go to the <code>C:\msys\1.0\home\<windows login>\synfig\_src</code> directory. Get the latest sources of Synfig from its repository.

:: <code>'''$ svn co <nowiki>https://synfig.svn.sourceforge.net/svnroot/synfig/ETL/trunk/ </nowiki> ETL'''</code> 
:: <code>'''$ svn co <nowiki>https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-core/trunk/ </nowiki> synfig-core'''</code> 
:: <code>'''$ svn co <nowiki>https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-studio/trunk/ </nowiki> synfig-studio'''</code> 

'''Note:''' The commands have a space between the URL address and the third paramater, it's easy to miss it. There should be three, space separated, paramaters in total after the "'''svn'''" command.

Download the current stable [http://www.openexr.com/ OpenEXR] version from:

* http://download.savannah.gnu.org/releases-noredirect/openexr/ilmbase-1.0.1.tar.gz (452 KB)
* http://download.savannah.gnu.org/releases-noredirect/openexr/openexr-1.6.1.tar.gz (13 MB)

Finally, you must have three directories (ETL, synfig-core and synfig-studio) and the ilmbase-1.0.1.tar.gz & openexr-1.6.1.tar.gz files in your <code>'''_src'''</code> directory.

===_filez directory===
Save the following text as <code>C:\msys\1.0\home\<windows login>\synfig\_filez\synfig-core-hack-libtool.patch</code>:
<code><pre><nowiki>
diff -Nuar synfig-core.orig/win32build/libtool synfig-core/win32build/libtool
--- synfig-core.orig/win32build/libtool Wed Feb 7 21:52:34 2007
+++ synfig-core/win32build/libtool Wed Feb 7 21:57:12 2007
@@ -2805,7 +2805,7 @@
fi
elif test "$build_libtool_libs" = yes; then
# Not a shared library
- if test "$deplibs_check_method" != pass_all; then
+ if test "$deplibs_check_method" != pass_all && test "$old_library" != "libltdl.a"; then
# We're trying link a shared library against a static one
# but the system doesn't support it.

</nowiki></pre></code>

Then save the following as <code>C:\msys\1.0\home\<windows login>\synfig\_filez\ilmbase-1.0.1-makefile.patch</code>:
<code><pre><nowiki>
diff -Nuar ilmbase-1.0.1.orig/IlmThread/Makefile.in ilmbase-1.0.1/IlmThread/Makefile.in
--- ilmbase-1.0.1.orig/IlmThread/Makefile.in Tue Oct 9 14:28:29 2007
+++ ilmbase-1.0.1/IlmThread/Makefile.in Sat Aug 16 18:35:08 2008
@@ -64,7 +64,8 @@
am_libIlmThread_la_OBJECTS = IlmThreadPool.lo IlmThread.lo \
IlmThreadSemaphore.lo IlmThreadMutex.lo IlmThreadPosix.lo \
IlmThreadSemaphorePosix.lo IlmThreadSemaphorePosixCompat.lo \
- IlmThreadMutexPosix.lo
+ IlmThreadMutexPosix.lo IlmThreadWin32.lo IlmThreadSemaphoreWin32.lo \
+ IlmThreadMutexWin32.lo
libIlmThread_la_OBJECTS = $(am_libIlmThread_la_OBJECTS)
DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir)/config
depcomp = $(SHELL) $(top_srcdir)/depcomp
</nowiki></pre></code>

Finally save the following as <code>C:\msys\1.0\home\<windows login>\synfig\_filez\ilmbase-1.0.1-pkgconfig.patch</code>:
<code><pre><nowiki>
diff -Nuar ilmbase-1.0.1.orig/IlmBase.pc.in ilmbase-1.0.1/IlmBase.pc.in
--- ilmbase-1.0.1.orig/IlmBase.pc.in Wed Dec 13 14:55:53 2006
+++ ilmbase-1.0.1/IlmBase.pc.in Sat Aug 16 21:06:27 2008
@@ -7,5 +7,5 @@
Name: IlmBase
Description: Base math and exception libraries
Version: @ILMBASE_VERSION@
-Libs: -L${libdir} -lImath -lHalf -lIex -lIlmThread @PTHREAD_LIBS@
-Cflags: @PTHREAD_CFLAGS@ -I${OpenEXR_includedir}
+Libs: -L${libdir} -lImath -lHalf -lIex -lIlmThread
+Cflags: -I@includedir@ -I${OpenEXR_includedir}
</nowiki></pre></code>

Last but not least, prior to SVN 2055, the Windows installer files need patching - http://patches.synfig.org/r/3/

(Acknowledgment to the writer of http://qtpfsgui.wiki.sourceforge.net/Compiling+on+Windows for the tip on the b44ExpLogTable file in OpenEXR)

==Configuration==
This section describes the parameters of <code>synbuild.conf</code> file.

===Files and Directories===
As you can see in this section you can define the path and name of the special directories (with sources, patches and temporary directories). If you install the build scripts as written above, there is nothing to change.

Also this section contains the path and version of the OpenEXR source files.

===External tools===
In this section you need to define the path to the executable files of the three auxiliary packages: ImageMagick, Subversion and NSIS. ImageMagick and Subversion binaries are located using the PATH environment variable, but their paths are added to the end of the path list and so we can get name collisions. For example, the ImageMagick "convert" tool has the same name as the "convert" tool from Borland Delphi Explorer, which may have been installed before ImageMagick.

===Build setup===
'''MINGW_HOST''' - host parameter of "configure" script. Do not change it.

'''SYN_CORE_DEBUG_BUILD''' - if "yes", Synfig Core will be made with debug info.

'''SYN_STUDIO_DEBUG_BUILD''' - if "yes", Synfig Studio will be made with debug info.

===Patches===
In this section you can find a number of patch definition blocks, looking like this:

<table style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"><tr><td>
<pre># ETL patches
ETL_PATCHES=$(cat <<:END_ETL:
:END_ETL:)</pre></td></tr></table>

For example, if you place any filenames of patches between '':END_ETL:'' blocks, it will be applied before the configuration of ETL. Patch files need to be stored in the <code>_filez</code> directory.

This section is useful if you want to test your own patches before sending them to the Synfig developers.

===Autoconfiguration===
This section contatins code which sets up the required environment variables and (by default) there is no need to change anything.

==Build Order==
Note: If you want build synfig without slowing down other tasks running on the same machine while the build takes place, open a single msys session, then open "Task Manager", search for the ''sh.exe'' process and set its priority to "Below normal".

Note: Running an on-access antivirus scanner can dramatically decrease compilation speed.

===OpenEXR===
This package needs to be built only once. A rebuild is only required if you get a new version or want to apply a new patch to it or you update the compiler and it is incompatible with the previous binaries.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_openexr.sh</nowiki></blockquote>

Wait for the "Done: OpenEXR" message.

===ETL===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_etl.sh</nowiki></blockquote>

Wait for the "Done: ETL" message.

===Synfig Core===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_core.sh</nowiki></blockquote>

Wait for the "Done: synfig-core" message. It can take a long time. The Synfig Core installer will be moved into the current directory.

===Synfig Studio===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_studio.sh</nowiki></blockquote>

Wait for the "Done: synfig-studio" message. It can take a long time. The Synfig Studio installer will be moved into the current directory.

==Additional tools==
These tools are not required to build Synfig, but they can help in the debugging process.

P.S. Post this later. ;-)

(Atrus - keen to hear what you recommend for debug. Also any debug processes you go through to fix the bugs. There's several bugs (mainly preview rendering) that I see under the current builds of Windows that are not under Linux or the old 0.61.05 for Windows - Pxegeek 2/7/07)

[[Category:Windows]]

Dev:Building on Windows

2009-01-08T22:06:28Z

Creek23: /* _src directory */ format

[[Category:Building]]

==Directories==
If you didn't already install Mingw, [[Mingw installation|this page]] will guide you through the process.

If you didn't already start an msys session, do so now. Just double click the MSYS shortcut or run <code>'''C:\msys\1.0\msys.bat'''</code>. An msys session will be opened, creating your profile directory at <code>'''C:\msys\1.0\home\<windows login>'''</code>. As you can see, MinGW uses your windows login as the user name in its fake UNIX environment. Be careful, I've not checked whether it works with non latin-character account names.

Now, use explorer or your favorite file manager and go to <code>'''C:\msys\1.0\home\<windows login>'''</code>. Create a directory there for all Synfig operations. For example, let it be <code>'''synfig'''</code>. Go into this directory.

Ok, now you are at <code>'''C:\msys\1.0\home\<windows login>\synfig'''</code>. Create four directories here:
* <code>'''_filez'''</code>, for patches (and maybe later, additional files).
* <code>'''_src'''</code>, for program sources.
* <code>'''build'''</code>, for building programs.
* <code>'''temp'''</code>, for local installation programs and libraries, which are required for building synfig. (For example: ETL, synfig (core for studio), OpenEXR, etc...)

Of course, you can choose your own name for all the directories and choose their locations. All you need then is to set a new path in the configuration file. But for now we choose the easy way.

==Files==
Save this configuration file as <code>C:\msys\1.0\home\<windows login>\synfig\synbuild.conf</code>:

<code><pre><nowiki>
# Synfig for Win32 build configuration script.
#############################################################################
# 1. Files and Directories

# Uncompressed Synfig svn snapshots and another package sources
SYN_SOURCE_DIR=`dirname ~/.`"/synfig/_src"

# Directory additional files (patches f.e.)
SYN_FILEZ_DIR=`dirname ~/.`"/synfig/_filez"

# Temporary installations (ETL headers, synfig binaries for icon and image making)
SYN_TEMP_INSTALL=`dirname ~/.`"/synfig/temp"

# Build directory
SYN_BUILD_DIR=`dirname ~/.`"/synfig/build"

# OpenEXR source package
SYN_ILMBASE_VERSION="1.0.1"
SYN_ILMBASE_SRC="${SYN_SOURCE_DIR}/ilmbase-${SYN_ILMBASE_VERSION}.tar.gz"
SYN_OPENEXR_VERSION="1.6.1"
SYN_OPENEXR_SRC="${SYN_SOURCE_DIR}/openexr-${SYN_OPENEXR_VERSION}.tar.gz"

#############################################################################
# 2. External tools

# Path to ImageMagick directory.
SYN_IMAGEMAGICK_PATH="/C/Program Files/ImageMagick"

# Path to Subversion bin directory.
SYN_SUBVERSION_PATH="/C/Program Files/Subversion/bin"

# Path to NSIS directory with makensis.exe file.
SYN_NSIS_PATH="/C/Program Files/NSIS"

#############################################################################
# 3. Build setup

# Build host
MINGW_HOST="mingw32"

# Make debug build of Synfig Core
SYN_CORE_DEBUG_BUILD="no"

# Make debug build of Synfig Studio
SYN_STUDIO_DEBUG_BUILD="no"
#WITH_FMOD="yes"

#############################################################################
# 4. Patches (you can place here any additional patches)

# ETL patches
ETL_PATCHES=$(cat <<:END_ETL:
:END_ETL:)

# Synfig Core patches
SYNCORE_PATCHES=$(cat <<:END_SYNCORE:
:END_SYNCORE:)

# Sunfig Studio patches
SYNSTUDIO_PATCHES=$(cat <<:END_SYNSTUDIO:
:END_SYNSTUDIO:)

# OpenEXR ILMBase patches

ILMBASE_PATCHES=$(cat <<:END_ILMBASE:
ilmbase-1.0.1-makefile.patch
ilmbase-1.0.1-pkgconfig.patch
:END_ILMBASE:)

# OpenEXR patches
#openexr-1.4.0-pkgconfig.patch
#openexr-1.4.0-mingw32.patch
OPENEXR_PATCHES=$(cat <<:END_OPENEXR:
:END_OPENEXR:)

#############################################################################
# 5. Autoconfiguration

if [ "$GTK_BASEPATH" ]; then
CPPFLAGS="-I${GTK_BASEPATH}/include $CPPFLAGS"
fi

if [ "$SYN_IMAGEMAGICK_PATH" ]; then
PATH="${SYN_IMAGEMAGICK_PATH}:${PATH}"
fi

if [ "$SYN_SUBVERSION_PATH" ]; then
PATH="${SYN_SUBVERSION_PATH}:${PATH}"
fi

if [ "$SYN_NSIS_PATH" ]; then
PATH="${SYN_NSIS_PATH}:${PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/ETL" ]; then
PATH="${SYN_TEMP_INSTALL}/ETL/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/ETL/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/synfig-devel" ]; then
PATH="${SYN_TEMP_INSTALL}/synfig-devel/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/openexr" ]; then
PATH="${SYN_TEMP_INSTALL}/openexr/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/openexr/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

export PATH
export PKG_CONFIG_PATH
export CPPFLAGS
</nowiki></pre></code>

Save OpenEXR build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_openexr.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making OpenEXR..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/ilmbase-${SYN_ILMBASE_VERSION}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/ilmbase
[ $? -eq 0 ] || exit 1

rm -rf ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/openexr
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
echo PATH is $PATH
echo tar -xzf ${SYN_ILMBASE_SRC} -C ${SYN_BUILD_DIR}
tar -xzf ${SYN_ILMBASE_SRC} -C ${SYN_BUILD_DIR}
[ $? -eq 0 ] || exit 1
echo tar -xzf ${SYN_OPENEXR_SRC} -C ${SYN_BUILD_DIR}
tar -xzf ${SYN_OPENEXR_SRC} -C ${SYN_BUILD_DIR}
[ $? -eq 0 ] || exit 1

echo "Applying patches for ILMBase... "
cd ${SYN_BUILD_DIR}/ilmbase-${SYN_ILMBASE_VERSION}
[ $? -eq 0 ] || exit 1
for SFILE in ${ILMBASE_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring ILMbase"
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/openexr \
--disable-static --disable-threading --disable-posix-sem
[ $? -eq 0 ] || exit 1

echo "Making"
make
[ $? -eq 0 ] || exit 1
make install
[ $? -eq 0 ] || exit 1
echo "ILMBase Done"

echo "Applying patches for OpenEXR... "
cd ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
[ $? -eq 0 ] || exit 1
for SFILE in ${OPENEXR_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

# Now the temp/openexr dir exists, we can add it to paths
if [ -d "${SYN_TEMP_INSTALL}/openexr" ]; then
PATH="${SYN_TEMP_INSTALL}/openexr/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/openexr/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

export PATH
export PKG_CONFIG_PATH

echo "Configuring OpenEXR"
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/openexr \
--disable-static --disable-threading --disable-posix-sem --disable-ilmbasetest
[ $? -eq 0 ] || exit 1

echo "separately build b44ExpLogTable as the openexr script doesn't work under msys"
cd ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}/IlmImf
[ $? -eq 0 ] || exit 1
mingw32-g++ --verbose -g -O2 -I${SYN_TEMP_INSTALL}/openexr/include/OpenEXR -L${SYN_TEMP_INSTALL}/openexr/lib b44ExpLogTable.cpp -lHalf -o b44ExpLogTable
[ $? -eq 0 ] || exit 1
cd ..
[ $? -eq 0 ] || exit 1

echo "Making"
make
[ $? -eq 0 ] || exit 1
make install
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
# rm -rf ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
# [ $? -eq 0 ] || exit 1

echo "Done: OpenEXR"
</nowiki></pre></code>

Save ETL build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_etl.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making ETL..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/ETL
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/ETL/* ${SYN_BUILD_DIR}/ETL/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/ETL/.svn ${SYN_BUILD_DIR}/ETL/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
for SFILE in ${ETL_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
autoreconf -if
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/ETL
[ $? -eq 0 ] || exit 1

echo "Making"
make install
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1

echo "Done: ETL"
</nowiki></pre></code>

Save Synfig Core build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_core.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making Synfig-Core..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/synfig-devel
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-core/* ${SYN_BUILD_DIR}/synfig-core/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-core/.svn ${SYN_BUILD_DIR}/synfig-core/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
for SFILE in ${SYNCORE_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
libtoolize --ltdl --copy -f
autoreconf -if
[ $? -eq 0 ] || exit 1
mkdir win32build
[ $? -eq 0 ] || exit 1
cd win32build
[ $? -eq 0 ] || exit 1
if [ "$SYN_CORE_DEBUG_BUILD" == "yes" ]; then
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --disable-optimization --enable-debug
[ $? -eq 0 ] || exit 1
else
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --enable-optimization=1 --disable-debug
[ $? -eq 0 ] || exit 1
fi

echo "Making"
# libtool hack patch [begin]
patch -p2 <${SYN_FILEZ_DIR}/synfig-core-hack-libtool.patch
[ $? -eq 0 ] || exit 1
# libtool hack patch [end]
make package
[ $? -eq 0 ] || exit 1
mv ./synfig-*.exe ${CURRENT_DIR}/
[ $? -eq 0 ] || exit 1

make clean
[ $? -eq 0 ] || exit 1
# auto build hack installation [begin]
make install prefix=${SYN_TEMP_INSTALL}/synfig-devel
[ $? -eq 0 ] || exit 1
# auto build hack installation [end]
cd ${CURRENT_DIR}

# auto build hack patch [begin]
echo "Postprocessing"
SYN_SED_PATH=`echo ${SYN_TEMP_INSTALL}/synfig-devel | sed -e 's/\//\\\\\//g'`
[ $? -eq 0 ] || exit 1
mv ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp
[ $? -eq 0 ] || exit 1
sed -e "s/C:\/PROGRA~1\\/Synfig/${SYN_SED_PATH}/g" \
${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp >${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config
[ $? -eq 0 ] || exit 1
rm -f ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp
[ $? -eq 0 ] || exit 1
mv ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp
[ $? -eq 0 ] || exit 1
sed -e "s/C:\/PROGRA~1\\/Synfig/${SYN_SED_PATH}/g" \
${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp >${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc
[ $? -eq 0 ] || exit 1
rm -f ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp
[ $? -eq 0 ] || exit 1
# auto build hack patch [end]

rm -rf ${SYN_BUILD_DIR}/synfig-core

echo "Done: synfig-core"
</nowiki></pre></code>

Save Synfig Studio build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_studio.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making Synfig-Studio..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-studio/* ${SYN_BUILD_DIR}/synfig-studio/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-studio/.svn ${SYN_BUILD_DIR}/synfig-studio/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1
for SFILE in ${SYNSTUDIO_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
autoreconf -if
[ $? -eq 0 ] || exit 1
mkdir win32build
[ $? -eq 0 ] || exit 1
cd win32build
[ $? -eq 0 ] || exit 1
if [ "$SYN_STUDIO_DEBUG_BUILD" == "yes" ]; then
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --disable-optimization --enable-debug
[ $? -eq 0 ] || exit 1
else
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --enable-optimization=1 --disable-debug
[ $? -eq 0 ] || exit 1
fi

echo "Making"
make package
[ $? -eq 0 ] || exit 1

mv ./synfigstudio-*.exe ${CURRENT_DIR}/
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1

echo "Done: synfig-studio"
</nowiki></pre></code>

===_src directory===
Go to the <code>C:\msys\1.0\home\<windows login>\synfig\_src</code> directory. Get the latest sources of Synfig from its repository.

:: <code>'''$ svn co <nowiki>https://synfig.svn.sourceforge.net/svnroot/synfig/ETL/trunk/ </nowiki> ETL'''</code> 
:: <code>'''$ svn co <nowiki>https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-core/trunk/ </nowiki> synfig-core'''</code> 
:: <code>'''$ svn co <nowiki>https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-studio/trunk/ </nowiki> synfig-studio'''</code> 

'''Note:''' The commands have a space between the URL address and the third paramater, it's easy to miss it. There should be three, space separated, paramaters in total after the "'''svn'''" command.

Download the current stable [http://www.openexr.com/ OpenEXR] version from:

* http://download.savannah.nongnu.org/releases/openexr/ilmbase-1.0.1.tar.gz (452KB)
* http://download.savannah.nongnu.org/releases/openexr/openexr-1.6.1.tar.gz (13 MB)

Finally you must have three directories (ETL, synfig-core and synfig-studio) and the ilmbase-1.0.1.tar.gz & openexr-1.6.1.tar.gz files in your <code>'''_src'''</code> directory.

===_filez directory===
Save the following text as <code>C:\msys\1.0\home\<windows login>\synfig\_filez\synfig-core-hack-libtool.patch</code>:
<code><pre><nowiki>
diff -Nuar synfig-core.orig/win32build/libtool synfig-core/win32build/libtool
--- synfig-core.orig/win32build/libtool Wed Feb 7 21:52:34 2007
+++ synfig-core/win32build/libtool Wed Feb 7 21:57:12 2007
@@ -2805,7 +2805,7 @@
fi
elif test "$build_libtool_libs" = yes; then
# Not a shared library
- if test "$deplibs_check_method" != pass_all; then
+ if test "$deplibs_check_method" != pass_all && test "$old_library" != "libltdl.a"; then
# We're trying link a shared library against a static one
# but the system doesn't support it.

</nowiki></pre></code>

Then save the following as <code>C:\msys\1.0\home\<windows login>\synfig\_filez\ilmbase-1.0.1-makefile.patch</code>:
<code><pre><nowiki>
diff -Nuar ilmbase-1.0.1.orig/IlmThread/Makefile.in ilmbase-1.0.1/IlmThread/Makefile.in
--- ilmbase-1.0.1.orig/IlmThread/Makefile.in Tue Oct 9 14:28:29 2007
+++ ilmbase-1.0.1/IlmThread/Makefile.in Sat Aug 16 18:35:08 2008
@@ -64,7 +64,8 @@
am_libIlmThread_la_OBJECTS = IlmThreadPool.lo IlmThread.lo \
IlmThreadSemaphore.lo IlmThreadMutex.lo IlmThreadPosix.lo \
IlmThreadSemaphorePosix.lo IlmThreadSemaphorePosixCompat.lo \
- IlmThreadMutexPosix.lo
+ IlmThreadMutexPosix.lo IlmThreadWin32.lo IlmThreadSemaphoreWin32.lo \
+ IlmThreadMutexWin32.lo
libIlmThread_la_OBJECTS = $(am_libIlmThread_la_OBJECTS)
DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir)/config
depcomp = $(SHELL) $(top_srcdir)/depcomp
</nowiki></pre></code>

Finally save the following as <code>C:\msys\1.0\home\<windows login>\synfig\_filez\ilmbase-1.0.1-pkgconfig.patch</code>:
<code><pre><nowiki>
diff -Nuar ilmbase-1.0.1.orig/IlmBase.pc.in ilmbase-1.0.1/IlmBase.pc.in
--- ilmbase-1.0.1.orig/IlmBase.pc.in Wed Dec 13 14:55:53 2006
+++ ilmbase-1.0.1/IlmBase.pc.in Sat Aug 16 21:06:27 2008
@@ -7,5 +7,5 @@
Name: IlmBase
Description: Base math and exception libraries
Version: @ILMBASE_VERSION@
-Libs: -L${libdir} -lImath -lHalf -lIex -lIlmThread @PTHREAD_LIBS@
-Cflags: @PTHREAD_CFLAGS@ -I${OpenEXR_includedir}
+Libs: -L${libdir} -lImath -lHalf -lIex -lIlmThread
+Cflags: -I@includedir@ -I${OpenEXR_includedir}
</nowiki></pre></code>

Last but not least, prior to SVN 2055, the Windows installer files need patching - http://patches.synfig.org/r/3/

(Acknowledgment to the writer of http://qtpfsgui.wiki.sourceforge.net/Compiling+on+Windows for the tip on the b44ExpLogTable file in OpenEXR)

==Configuration==
This section describes the parameters of <code>synbuild.conf</code> file.

===Files and Directories===
As you can see in this section you can define the path and name of the special directories (with sources, patches and temporary directories). If you install the build scripts as written above, there is nothing to change.

Also this section contains the path and version of the OpenEXR source files.

===External tools===
In this section you need to define the path to the executable files of the three auxiliary packages: ImageMagick, Subversion and NSIS. ImageMagick and Subversion binaries are located using the PATH environment variable, but their paths are added to the end of the path list and so we can get name collisions. For example, the ImageMagick "convert" tool has the same name as the "convert" tool from Borland Delphi Explorer, which may have been installed before ImageMagick.

===Build setup===
'''MINGW_HOST''' - host parameter of "configure" script. Do not change it.

'''SYN_CORE_DEBUG_BUILD''' - if "yes", Synfig Core will be made with debug info.

'''SYN_STUDIO_DEBUG_BUILD''' - if "yes", Synfig Studio will be made with debug info.

===Patches===
In this section you can find a number of patch definition blocks, looking like this:

<table style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"><tr><td>
<pre># ETL patches
ETL_PATCHES=$(cat <<:END_ETL:
:END_ETL:)</pre></td></tr></table>

For example, if you place any filenames of patches between '':END_ETL:'' blocks, it will be applied before the configuration of ETL. Patch files need to be stored in the <code>_filez</code> directory.

This section is useful if you want to test your own patches before sending them to the Synfig developers.

===Autoconfiguration===
This section contatins code which sets up the required environment variables and (by default) there is no need to change anything.

==Build Order==
Note: If you want build synfig without slowing down other tasks running on the same machine while the build takes place, open a single msys session, then open "Task Manager", search for the ''sh.exe'' process and set its priority to "Below normal".

Note: Running an on-access antivirus scanner can dramatically decrease compilation speed.

===OpenEXR===
This package needs to be built only once. A rebuild is only required if you get a new version or want to apply a new patch to it or you update the compiler and it is incompatible with the previous binaries.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_openexr.sh</nowiki></blockquote>

Wait for the "Done: OpenEXR" message.

===ETL===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_etl.sh</nowiki></blockquote>

Wait for the "Done: ETL" message.

===Synfig Core===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_core.sh</nowiki></blockquote>

Wait for the "Done: synfig-core" message. It can take a long time. The Synfig Core installer will be moved into the current directory.

===Synfig Studio===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_studio.sh</nowiki></blockquote>

Wait for the "Done: synfig-studio" message. It can take a long time. The Synfig Studio installer will be moved into the current directory.

==Additional tools==
These tools are not required to build Synfig, but they can help in the debugging process.

P.S. Post this later. ;-)

(Atrus - keen to hear what you recommend for debug. Also any debug processes you go through to fix the bugs. There's several bugs (mainly preview rendering) that I see under the current builds of Windows that are not under Linux or the old 0.61.05 for Windows - Pxegeek 2/7/07)

[[Category:Windows]]

Dev:Building on Windows

2009-01-08T21:40:34Z

Creek23: /* Directories */ hilight

[[Category:Building]]

==Directories==
If you didn't already install Mingw, [[Mingw installation|this page]] will guide you through the process.

If you didn't already start an msys session, do so now. Just double click the MSYS shortcut or run <code>'''C:\msys\1.0\msys.bat'''</code>. An msys session will be opened, creating your profile directory at <code>'''C:\msys\1.0\home\<windows login>'''</code>. As you can see, MinGW uses your windows login as the user name in its fake UNIX environment. Be careful, I've not checked whether it works with non latin-character account names.

Now, use explorer or your favorite file manager and go to <code>'''C:\msys\1.0\home\<windows login>'''</code>. Create a directory there for all Synfig operations. For example, let it be <code>'''synfig'''</code>. Go into this directory.

Ok, now you are at <code>'''C:\msys\1.0\home\<windows login>\synfig'''</code>. Create four directories here:
* <code>'''_filez'''</code>, for patches (and maybe later, additional files).
* <code>'''_src'''</code>, for program sources.
* <code>'''build'''</code>, for building programs.
* <code>'''temp'''</code>, for local installation programs and libraries, which are required for building synfig. (For example: ETL, synfig (core for studio), OpenEXR, etc...)

Of course, you can choose your own name for all the directories and choose their locations. All you need then is to set a new path in the configuration file. But for now we choose the easy way.

==Files==
Save this configuration file as <code>C:\msys\1.0\home\<windows login>\synfig\synbuild.conf</code>:

<code><pre><nowiki>
# Synfig for Win32 build configuration script.
#############################################################################
# 1. Files and Directories

# Uncompressed Synfig svn snapshots and another package sources
SYN_SOURCE_DIR=`dirname ~/.`"/synfig/_src"

# Directory additional files (patches f.e.)
SYN_FILEZ_DIR=`dirname ~/.`"/synfig/_filez"

# Temporary installations (ETL headers, synfig binaries for icon and image making)
SYN_TEMP_INSTALL=`dirname ~/.`"/synfig/temp"

# Build directory
SYN_BUILD_DIR=`dirname ~/.`"/synfig/build"

# OpenEXR source package
SYN_ILMBASE_VERSION="1.0.1"
SYN_ILMBASE_SRC="${SYN_SOURCE_DIR}/ilmbase-${SYN_ILMBASE_VERSION}.tar.gz"
SYN_OPENEXR_VERSION="1.6.1"
SYN_OPENEXR_SRC="${SYN_SOURCE_DIR}/openexr-${SYN_OPENEXR_VERSION}.tar.gz"

#############################################################################
# 2. External tools

# Path to ImageMagick directory.
SYN_IMAGEMAGICK_PATH="/C/Program Files/ImageMagick"

# Path to Subversion bin directory.
SYN_SUBVERSION_PATH="/C/Program Files/Subversion/bin"

# Path to NSIS directory with makensis.exe file.
SYN_NSIS_PATH="/C/Program Files/NSIS"

#############################################################################
# 3. Build setup

# Build host
MINGW_HOST="mingw32"

# Make debug build of Synfig Core
SYN_CORE_DEBUG_BUILD="no"

# Make debug build of Synfig Studio
SYN_STUDIO_DEBUG_BUILD="no"
#WITH_FMOD="yes"

#############################################################################
# 4. Patches (you can place here any additional patches)

# ETL patches
ETL_PATCHES=$(cat <<:END_ETL:
:END_ETL:)

# Synfig Core patches
SYNCORE_PATCHES=$(cat <<:END_SYNCORE:
:END_SYNCORE:)

# Sunfig Studio patches
SYNSTUDIO_PATCHES=$(cat <<:END_SYNSTUDIO:
:END_SYNSTUDIO:)

# OpenEXR ILMBase patches

ILMBASE_PATCHES=$(cat <<:END_ILMBASE:
ilmbase-1.0.1-makefile.patch
ilmbase-1.0.1-pkgconfig.patch
:END_ILMBASE:)

# OpenEXR patches
#openexr-1.4.0-pkgconfig.patch
#openexr-1.4.0-mingw32.patch
OPENEXR_PATCHES=$(cat <<:END_OPENEXR:
:END_OPENEXR:)

#############################################################################
# 5. Autoconfiguration

if [ "$GTK_BASEPATH" ]; then
CPPFLAGS="-I${GTK_BASEPATH}/include $CPPFLAGS"
fi

if [ "$SYN_IMAGEMAGICK_PATH" ]; then
PATH="${SYN_IMAGEMAGICK_PATH}:${PATH}"
fi

if [ "$SYN_SUBVERSION_PATH" ]; then
PATH="${SYN_SUBVERSION_PATH}:${PATH}"
fi

if [ "$SYN_NSIS_PATH" ]; then
PATH="${SYN_NSIS_PATH}:${PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/ETL" ]; then
PATH="${SYN_TEMP_INSTALL}/ETL/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/ETL/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/synfig-devel" ]; then
PATH="${SYN_TEMP_INSTALL}/synfig-devel/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

if [ -d "${SYN_TEMP_INSTALL}/openexr" ]; then
PATH="${SYN_TEMP_INSTALL}/openexr/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/openexr/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

export PATH
export PKG_CONFIG_PATH
export CPPFLAGS
</nowiki></pre></code>

Save OpenEXR build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_openexr.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making OpenEXR..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/ilmbase-${SYN_ILMBASE_VERSION}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/ilmbase
[ $? -eq 0 ] || exit 1

rm -rf ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/openexr
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
echo PATH is $PATH
echo tar -xzf ${SYN_ILMBASE_SRC} -C ${SYN_BUILD_DIR}
tar -xzf ${SYN_ILMBASE_SRC} -C ${SYN_BUILD_DIR}
[ $? -eq 0 ] || exit 1
echo tar -xzf ${SYN_OPENEXR_SRC} -C ${SYN_BUILD_DIR}
tar -xzf ${SYN_OPENEXR_SRC} -C ${SYN_BUILD_DIR}
[ $? -eq 0 ] || exit 1

echo "Applying patches for ILMBase... "
cd ${SYN_BUILD_DIR}/ilmbase-${SYN_ILMBASE_VERSION}
[ $? -eq 0 ] || exit 1
for SFILE in ${ILMBASE_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring ILMbase"
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/openexr \
--disable-static --disable-threading --disable-posix-sem
[ $? -eq 0 ] || exit 1

echo "Making"
make
[ $? -eq 0 ] || exit 1
make install
[ $? -eq 0 ] || exit 1
echo "ILMBase Done"

echo "Applying patches for OpenEXR... "
cd ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
[ $? -eq 0 ] || exit 1
for SFILE in ${OPENEXR_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

# Now the temp/openexr dir exists, we can add it to paths
if [ -d "${SYN_TEMP_INSTALL}/openexr" ]; then
PATH="${SYN_TEMP_INSTALL}/openexr/bin:${PATH}"
PKG_CONFIG_PATH="${SYN_TEMP_INSTALL}/openexr/lib/pkgconfig:${PKG_CONFIG_PATH}"
fi

export PATH
export PKG_CONFIG_PATH

echo "Configuring OpenEXR"
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/openexr \
--disable-static --disable-threading --disable-posix-sem --disable-ilmbasetest
[ $? -eq 0 ] || exit 1

echo "separately build b44ExpLogTable as the openexr script doesn't work under msys"
cd ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}/IlmImf
[ $? -eq 0 ] || exit 1
mingw32-g++ --verbose -g -O2 -I${SYN_TEMP_INSTALL}/openexr/include/OpenEXR -L${SYN_TEMP_INSTALL}/openexr/lib b44ExpLogTable.cpp -lHalf -o b44ExpLogTable
[ $? -eq 0 ] || exit 1
cd ..
[ $? -eq 0 ] || exit 1

echo "Making"
make
[ $? -eq 0 ] || exit 1
make install
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
# rm -rf ${SYN_BUILD_DIR}/openexr-${SYN_OPENEXR_VERSION}
# [ $? -eq 0 ] || exit 1

echo "Done: OpenEXR"
</nowiki></pre></code>

Save ETL build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_etl.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making ETL..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/ETL
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/ETL/* ${SYN_BUILD_DIR}/ETL/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/ETL/.svn ${SYN_BUILD_DIR}/ETL/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1
for SFILE in ${ETL_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
autoreconf -if
[ $? -eq 0 ] || exit 1
./configure --host=${MINGW_HOST} --prefix=${SYN_TEMP_INSTALL}/ETL
[ $? -eq 0 ] || exit 1

echo "Making"
make install
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_BUILD_DIR}/ETL
[ $? -eq 0 ] || exit 1

echo "Done: ETL"
</nowiki></pre></code>

Save Synfig Core build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_core.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making Synfig-Core..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_TEMP_INSTALL}/synfig-devel
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-core/* ${SYN_BUILD_DIR}/synfig-core/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-core/.svn ${SYN_BUILD_DIR}/synfig-core/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/synfig-core
[ $? -eq 0 ] || exit 1
for SFILE in ${SYNCORE_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
libtoolize --ltdl --copy -f
autoreconf -if
[ $? -eq 0 ] || exit 1
mkdir win32build
[ $? -eq 0 ] || exit 1
cd win32build
[ $? -eq 0 ] || exit 1
if [ "$SYN_CORE_DEBUG_BUILD" == "yes" ]; then
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --disable-optimization --enable-debug
[ $? -eq 0 ] || exit 1
else
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --enable-optimization=1 --disable-debug
[ $? -eq 0 ] || exit 1
fi

echo "Making"
# libtool hack patch [begin]
patch -p2 <${SYN_FILEZ_DIR}/synfig-core-hack-libtool.patch
[ $? -eq 0 ] || exit 1
# libtool hack patch [end]
make package
[ $? -eq 0 ] || exit 1
mv ./synfig-*.exe ${CURRENT_DIR}/
[ $? -eq 0 ] || exit 1

make clean
[ $? -eq 0 ] || exit 1
# auto build hack installation [begin]
make install prefix=${SYN_TEMP_INSTALL}/synfig-devel
[ $? -eq 0 ] || exit 1
# auto build hack installation [end]
cd ${CURRENT_DIR}

# auto build hack patch [begin]
echo "Postprocessing"
SYN_SED_PATH=`echo ${SYN_TEMP_INSTALL}/synfig-devel | sed -e 's/\//\\\\\//g'`
[ $? -eq 0 ] || exit 1
mv ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp
[ $? -eq 0 ] || exit 1
sed -e "s/C:\/PROGRA~1\\/Synfig/${SYN_SED_PATH}/g" \
${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp >${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config
[ $? -eq 0 ] || exit 1
rm -f ${SYN_TEMP_INSTALL}/synfig-devel/bin/synfig-config.tmp
[ $? -eq 0 ] || exit 1
mv ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp
[ $? -eq 0 ] || exit 1
sed -e "s/C:\/PROGRA~1\\/Synfig/${SYN_SED_PATH}/g" \
${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp >${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc
[ $? -eq 0 ] || exit 1
rm -f ${SYN_TEMP_INSTALL}/synfig-devel/lib/pkgconfig/synfig.pc.tmp
[ $? -eq 0 ] || exit 1
# auto build hack patch [end]

rm -rf ${SYN_BUILD_DIR}/synfig-core

echo "Done: synfig-core"
</nowiki></pre></code>

Save Synfig Studio build script as <code>C:\msys\1.0\home\<windows login>\synfig\make_studio.sh</code>:
<code><pre><nowiki>
#!/bin/sh

echo "Making Synfig-Studio..."
# Including configuration
if [ -r "./synbuild.conf" ]; then
. ./synbuild.conf
else
echo "No config file for synfig build (./synbuild.conf) found."
exit 1
fi

CURRENT_DIR=`pwd`

echo "Cleanup directories"
rm -rf ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1

echo "Preparing sources"
mkdir ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-studio/* ${SYN_BUILD_DIR}/synfig-studio/
[ $? -eq 0 ] || exit 1
cp -R ${SYN_SOURCE_DIR}/synfig-studio/.svn ${SYN_BUILD_DIR}/synfig-studio/
[ $? -eq 0 ] || exit 1

echo "Applying patches..."
cd ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1
for SFILE in ${SYNSTUDIO_PATCHES[@]}
do
patch -p1 <${SYN_FILEZ_DIR}/${SFILE}
[ $? -eq 0 ] || exit 1
done

echo "Configuring"
autoreconf -if
[ $? -eq 0 ] || exit 1
mkdir win32build
[ $? -eq 0 ] || exit 1
cd win32build
[ $? -eq 0 ] || exit 1
if [ "$SYN_STUDIO_DEBUG_BUILD" == "yes" ]; then
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --disable-optimization --enable-debug
[ $? -eq 0 ] || exit 1
else
../configure --host=${MINGW_HOST} --prefix=C:/PROGRA~1/Synfig --enable-optimization=1 --disable-debug
[ $? -eq 0 ] || exit 1
fi

echo "Making"
make package
[ $? -eq 0 ] || exit 1

mv ./synfigstudio-*.exe ${CURRENT_DIR}/
[ $? -eq 0 ] || exit 1
cd ${CURRENT_DIR}
[ $? -eq 0 ] || exit 1
rm -rf ${SYN_BUILD_DIR}/synfig-studio
[ $? -eq 0 ] || exit 1

echo "Done: synfig-studio"
</nowiki></pre></code>

===_src directory===
Go to the <code>C:\msys\1.0\home\<windows login>\synfig\_src</code> directory. Get the latest sources of Synfig from its repository.

<blockquote><nowiki>$ svn co https://synfig.svn.sourceforge.net/svnroot/synfig/ETL/trunk/ ETL</nowiki> 
<nowiki>$ svn co https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-core/trunk/ synfig-core</nowiki> 
<nowiki>$ svn co https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-studio/trunk/ synfig-studio</nowiki></blockquote>

Note: The commands have a space between the URL address and the third paramater, it's easy to miss it. There should be three, space separated, paramaters in total after the "svn" command.

Download the current stable [http://www.openexr.com/ OpenEXR] version from:

* http://download.savannah.nongnu.org/releases/openexr/ilmbase-1.0.1.tar.gz (452KB)
* http://download.savannah.nongnu.org/releases/openexr/openexr-1.6.1.tar.gz (13 MB)

Finally you must have three directories (ETL, synfig-core and synfig-studio) and the ilmbase-1.0.1.tar.gz & openexr-1.6.1.tar.gz files in your <code>_src</code> directory.

===_filez directory===
Save the following text as <code>C:\msys\1.0\home\<windows login>\synfig\_filez\synfig-core-hack-libtool.patch</code>:
<code><pre><nowiki>
diff -Nuar synfig-core.orig/win32build/libtool synfig-core/win32build/libtool
--- synfig-core.orig/win32build/libtool Wed Feb 7 21:52:34 2007
+++ synfig-core/win32build/libtool Wed Feb 7 21:57:12 2007
@@ -2805,7 +2805,7 @@
fi
elif test "$build_libtool_libs" = yes; then
# Not a shared library
- if test "$deplibs_check_method" != pass_all; then
+ if test "$deplibs_check_method" != pass_all && test "$old_library" != "libltdl.a"; then
# We're trying link a shared library against a static one
# but the system doesn't support it.

</nowiki></pre></code>

Then save the following as <code>C:\msys\1.0\home\<windows login>\synfig\_filez\ilmbase-1.0.1-makefile.patch</code>:
<code><pre><nowiki>
diff -Nuar ilmbase-1.0.1.orig/IlmThread/Makefile.in ilmbase-1.0.1/IlmThread/Makefile.in
--- ilmbase-1.0.1.orig/IlmThread/Makefile.in Tue Oct 9 14:28:29 2007
+++ ilmbase-1.0.1/IlmThread/Makefile.in Sat Aug 16 18:35:08 2008
@@ -64,7 +64,8 @@
am_libIlmThread_la_OBJECTS = IlmThreadPool.lo IlmThread.lo \
IlmThreadSemaphore.lo IlmThreadMutex.lo IlmThreadPosix.lo \
IlmThreadSemaphorePosix.lo IlmThreadSemaphorePosixCompat.lo \
- IlmThreadMutexPosix.lo
+ IlmThreadMutexPosix.lo IlmThreadWin32.lo IlmThreadSemaphoreWin32.lo \
+ IlmThreadMutexWin32.lo
libIlmThread_la_OBJECTS = $(am_libIlmThread_la_OBJECTS)
DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir)/config
depcomp = $(SHELL) $(top_srcdir)/depcomp
</nowiki></pre></code>

Finally save the following as <code>C:\msys\1.0\home\<windows login>\synfig\_filez\ilmbase-1.0.1-pkgconfig.patch</code>:
<code><pre><nowiki>
diff -Nuar ilmbase-1.0.1.orig/IlmBase.pc.in ilmbase-1.0.1/IlmBase.pc.in
--- ilmbase-1.0.1.orig/IlmBase.pc.in Wed Dec 13 14:55:53 2006
+++ ilmbase-1.0.1/IlmBase.pc.in Sat Aug 16 21:06:27 2008
@@ -7,5 +7,5 @@
Name: IlmBase
Description: Base math and exception libraries
Version: @ILMBASE_VERSION@
-Libs: -L${libdir} -lImath -lHalf -lIex -lIlmThread @PTHREAD_LIBS@
-Cflags: @PTHREAD_CFLAGS@ -I${OpenEXR_includedir}
+Libs: -L${libdir} -lImath -lHalf -lIex -lIlmThread
+Cflags: -I@includedir@ -I${OpenEXR_includedir}
</nowiki></pre></code>

Last but not least, prior to SVN 2055, the Windows installer files need patching - http://patches.synfig.org/r/3/

(Acknowledgment to the writer of http://qtpfsgui.wiki.sourceforge.net/Compiling+on+Windows for the tip on the b44ExpLogTable file in OpenEXR)

==Configuration==
This section describes the parameters of <code>synbuild.conf</code> file.

===Files and Directories===
As you can see in this section you can define the path and name of the special directories (with sources, patches and temporary directories). If you install the build scripts as written above, there is nothing to change.

Also this section contains the path and version of the OpenEXR source files.

===External tools===
In this section you need to define the path to the executable files of the three auxiliary packages: ImageMagick, Subversion and NSIS. ImageMagick and Subversion binaries are located using the PATH environment variable, but their paths are added to the end of the path list and so we can get name collisions. For example, the ImageMagick "convert" tool has the same name as the "convert" tool from Borland Delphi Explorer, which may have been installed before ImageMagick.

===Build setup===
'''MINGW_HOST''' - host parameter of "configure" script. Do not change it.

'''SYN_CORE_DEBUG_BUILD''' - if "yes", Synfig Core will be made with debug info.

'''SYN_STUDIO_DEBUG_BUILD''' - if "yes", Synfig Studio will be made with debug info.

===Patches===
In this section you can find a number of patch definition blocks, looking like this:

<table style="padding: 1em; border: 1px dashed #2f6fab; color: Black; background-color: #f9f9f9; line-height: 1.1em;"><tr><td>
<pre># ETL patches
ETL_PATCHES=$(cat <<:END_ETL:
:END_ETL:)</pre></td></tr></table>

For example, if you place any filenames of patches between '':END_ETL:'' blocks, it will be applied before the configuration of ETL. Patch files need to be stored in the <code>_filez</code> directory.

This section is useful if you want to test your own patches before sending them to the Synfig developers.

===Autoconfiguration===
This section contatins code which sets up the required environment variables and (by default) there is no need to change anything.

==Build Order==
Note: If you want build synfig without slowing down other tasks running on the same machine while the build takes place, open a single msys session, then open "Task Manager", search for the ''sh.exe'' process and set its priority to "Below normal".

Note: Running an on-access antivirus scanner can dramatically decrease compilation speed.

===OpenEXR===
This package needs to be built only once. A rebuild is only required if you get a new version or want to apply a new patch to it or you update the compiler and it is incompatible with the previous binaries.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_openexr.sh</nowiki></blockquote>

Wait for the "Done: OpenEXR" message.

===ETL===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_etl.sh</nowiki></blockquote>

Wait for the "Done: ETL" message.

===Synfig Core===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_core.sh</nowiki></blockquote>

Wait for the "Done: synfig-core" message. It can take a long time. The Synfig Core installer will be moved into the current directory.

===Synfig Studio===
Rebuild it when you get a new version of Synfig.

In your msys console go to the <code>C:\msys\1.0\home\<windows login>\synfig</code> directory by typing:

<blockquote><nowiki>$ cd ~/synfig</nowiki></blockquote>

Then type:

<blockquote><nowiki>$ ./make_studio.sh</nowiki></blockquote>

Wait for the "Done: synfig-studio" message. It can take a long time. The Synfig Studio installer will be moved into the current directory.

==Additional tools==
These tools are not required to build Synfig, but they can help in the debugging process.

P.S. Post this later. ;-)

(Atrus - keen to hear what you recommend for debug. Also any debug processes you go through to fix the bugs. There's several bugs (mainly preview rendering) that I see under the current builds of Windows that are not under Linux or the old 0.61.05 for Windows - Pxegeek 2/7/07)

[[Category:Windows]]

Dev:Mingw installation

2009-01-08T21:34:10Z

Creek23: /* [http://www.gtkmm.org/ GTKmm] */ added other link

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 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]===
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]===
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:

* libsigc++
* cairomm
* glibmm
* gtkmm
* libxml++

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.

Dev:Mingw installation

2009-01-08T20:47:15Z

Creek23: /* [http://www.gtk.org/ GTK+] */ KB -> MB

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 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]===
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]===
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)

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 <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.

Dev:Mingw installation

2009-01-08T20:35:12Z

Creek23: /* [http://www.gtk.org/ GTK+] */ added filesize

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 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]===
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]===
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 (17,172 KB)
* 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)

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 <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.

Dev:Mingw installation

2009-01-08T20:33:26Z

Creek23: /* [http://www.imagemagick.org ImageMagick] */ changed link

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 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]===
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]===
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
* http://downloads.sourceforge.net/gladewin32/gtk-dev-2.12.9-win32-1.exe

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)

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 <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.

Dev:Mingw installation

2009-01-08T20:28:03Z

Creek23: /* [http://www.winterdrache.de/freeware/png2ico/index.html png2ico] */ format

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 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]===
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]===
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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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
* http://downloads.sourceforge.net/gladewin32/gtk-dev-2.12.9-win32-1.exe

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)

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 <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.

Dev:Mingw installation

2009-01-08T20:25:30Z

Creek23: /* [http://www.mktemp.org/ mktemp] */ hilight

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 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]===
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]===
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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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
* http://downloads.sourceforge.net/gladewin32/gtk-dev-2.12.9-win32-1.exe

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)

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 <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.

Dev:Mingw installation

2009-01-08T20:22:39Z

Creek23: /* [http://darwinsys.com/file/ file] */ format

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 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]===
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]===
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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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
* http://downloads.sourceforge.net/gladewin32/gtk-dev-2.12.9-win32-1.exe

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)

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 <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.

Dev:Mingw installation

2009-01-08T20:21:29Z

Creek23: /* [http://www.mktemp.org/ mktemp] */ format

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 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)

and 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]===
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]===
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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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
* http://downloads.sourceforge.net/gladewin32/gtk-dev-2.12.9-win32-1.exe

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)

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 <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.

Dev:Mingw installation

2009-01-08T20:15:31Z

Creek23: /* [http://www.gnu.org/software/gettext Gettext] */ aded link

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 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)

and 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]===
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]===
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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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
* http://downloads.sourceforge.net/gladewin32/gtk-dev-2.12.9-win32-1.exe

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)

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 <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.

Dev:Mingw installation

2009-01-08T20:08:24Z

Creek23: /* [http://www.gnu.org/software/gettext Gettext] */ fixed link and new-format

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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.
# 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 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)

and 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]===
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]===
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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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
* http://downloads.sourceforge.net/gladewin32/gtk-dev-2.12.9-win32-1.exe

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)

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 <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.

Dev:Mingw installation

2009-01-08T19:35:33Z

Creek23: /* [http://www.gnu.org/software/libtool/ libtool] */ format

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 the [http://mirror.calvin.edu/cygwin/release/gettext/gettext-devel/ gettext-devel] package from the [http://www.cygwin.com/ Cygwin] project. Unpack the archive so that everything is under /usr/local instead of /usr. Note that any binaries that are not from the MinGW project or built specially for MSYS cannot be placed in the /msys/1.0/bin (/bin and /usr/bin inside MSYS) directory. You then need to hack the /usr/local/bin/autopoint script so that prefix is defined as /usr/local instead of /usr. Warning - ugly hack follows - Autopoint expects to find an archive.tar.gz in usr/share, so copy gettext (found on usr/share/ on the archive) file structure to /usr/share also.

Update: 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)

and 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]===
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]===
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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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
* http://downloads.sourceforge.net/gladewin32/gtk-dev-2.12.9-win32-1.exe

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)

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 <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.

Dev:Mingw installation

2009-01-08T18:01:19Z

Creek23: /* MSYS */ format

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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''' '''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 ]'''</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.''' '''Where is your MinGW installation?''' </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 the [http://mirror.calvin.edu/cygwin/release/gettext/gettext-devel/ gettext-devel] package from the [http://www.cygwin.com/ Cygwin] project. Unpack the archive so that everything is under /usr/local instead of /usr. Note that any binaries that are not from the MinGW project or built specially for MSYS cannot be placed in the /msys/1.0/bin (/bin and /usr/bin inside MSYS) directory. You then need to hack the /usr/local/bin/autopoint script so that prefix is defined as /usr/local instead of /usr. Warning - ugly hack follows - Autopoint expects to find an archive.tar.gz in usr/share, so copy gettext (found on usr/share/ on the archive) file structure to /usr/share also.

Update: 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)

and 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]===
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]===
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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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
* http://downloads.sourceforge.net/gladewin32/gtk-dev-2.12.9-win32-1.exe

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)

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 <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.

Dev:Mingw installation

2009-01-08T17:31:44Z

Creek23: /* [http://www.gtk.org/ GTK+] */ added possible GTK-Dev links

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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.

''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 "<code>c:/mingw</code>".

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 [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 the [http://mirror.calvin.edu/cygwin/release/gettext/gettext-devel/ gettext-devel] package from the [http://www.cygwin.com/ Cygwin] project. Unpack the archive so that everything is under /usr/local instead of /usr. Note that any binaries that are not from the MinGW project or built specially for MSYS cannot be placed in the /msys/1.0/bin (/bin and /usr/bin inside MSYS) directory. You then need to hack the /usr/local/bin/autopoint script so that prefix is defined as /usr/local instead of /usr. Warning - ugly hack follows - Autopoint expects to find an archive.tar.gz in usr/share, so copy gettext (found on usr/share/ on the archive) file structure to /usr/share also.

Update: 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)

and 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]===
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]===
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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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
* http://downloads.sourceforge.net/gladewin32/gtk-dev-2.12.9-win32-1.exe

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)

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 <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.

Dev:Mingw installation

2009-01-08T17:23:42Z

Creek23: /* [http://sourceforge.net/projects/nsis/ NSIS] */ updated link

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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.

''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 "<code>c:/mingw</code>".

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 [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 the [http://mirror.calvin.edu/cygwin/release/gettext/gettext-devel/ gettext-devel] package from the [http://www.cygwin.com/ Cygwin] project. Unpack the archive so that everything is under /usr/local instead of /usr. Note that any binaries that are not from the MinGW project or built specially for MSYS cannot be placed in the /msys/1.0/bin (/bin and /usr/bin inside MSYS) directory. You then need to hack the /usr/local/bin/autopoint script so that prefix is defined as /usr/local instead of /usr. Warning - ugly hack follows - Autopoint expects to find an archive.tar.gz in usr/share, so copy gettext (found on usr/share/ on the archive) file structure to /usr/share also.

Update: 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)

and 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]===
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]===
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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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

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)

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 <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.

Dev:Mingw installation

2009-01-08T17:09:57Z

Creek23: /* [http://www.gnu.org/software/automake/ automake] */ enlisted

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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.

''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 "<code>c:/mingw</code>".

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 [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 the [http://mirror.calvin.edu/cygwin/release/gettext/gettext-devel/ gettext-devel] package from the [http://www.cygwin.com/ Cygwin] project. Unpack the archive so that everything is under /usr/local instead of /usr. Note that any binaries that are not from the MinGW project or built specially for MSYS cannot be placed in the /msys/1.0/bin (/bin and /usr/bin inside MSYS) directory. You then need to hack the /usr/local/bin/autopoint script so that prefix is defined as /usr/local instead of /usr. Warning - ugly hack follows - Autopoint expects to find an archive.tar.gz in usr/share, so copy gettext (found on usr/share/ on the archive) file structure to /usr/share also.

Update: 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)

and 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]===
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]===
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.28-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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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

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)

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 <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.

Dev:Mingw installation

2009-01-08T17:07:33Z

Creek23: /* bash */ enlisted

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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.

''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 "<code>c:/mingw</code>".

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 [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 the [http://mirror.calvin.edu/cygwin/release/gettext/gettext-devel/ gettext-devel] package from the [http://www.cygwin.com/ Cygwin] project. Unpack the archive so that everything is under /usr/local instead of /usr. Note that any binaries that are not from the MinGW project or built specially for MSYS cannot be placed in the /msys/1.0/bin (/bin and /usr/bin inside MSYS) directory. You then need to hack the /usr/local/bin/autopoint script so that prefix is defined as /usr/local instead of /usr. Warning - ugly hack follows - Autopoint expects to find an archive.tar.gz in usr/share, so copy gettext (found on usr/share/ on the archive) file structure to /usr/share also.

Update: 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)

and 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]===
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]===
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.28-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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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

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)

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 <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.

Dev:Mingw installation

2009-01-08T17:02:02Z

Creek23: /* [http://www.gnu.org/software/autoconf/ autoconf] */ changed format

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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.

''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 "<code>c:/mingw</code>".

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 [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 the [http://mirror.calvin.edu/cygwin/release/gettext/gettext-devel/ gettext-devel] package from the [http://www.cygwin.com/ Cygwin] project. Unpack the archive so that everything is under /usr/local instead of /usr. Note that any binaries that are not from the MinGW project or built specially for MSYS cannot be placed in the /msys/1.0/bin (/bin and /usr/bin inside MSYS) directory. You then need to hack the /usr/local/bin/autopoint script so that prefix is defined as /usr/local instead of /usr. Warning - ugly hack follows - Autopoint expects to find an archive.tar.gz in usr/share, so copy gettext (found on usr/share/ on the archive) file structure to /usr/share also.

Update: 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)

and 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]===
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]===
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.28-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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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

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)

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 <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.

Dev:Mingw installation

2009-01-08T16:56:07Z

Creek23: /* bash */ re-worded

[[Category:Building]]
[[Category:Windows]]

==MinGW==
First - download [http://www.mingw.org/ MinGW] installer. You may get version 5.1.3 or higher (recommended).

* http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe (135.5 Kb)

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 <code>C:\MinGW</code>. If you install MinGW into another directory, synfig compilation may fail.

===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.

''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 "<code>c:/mingw</code>".

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 [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 the [http://mirror.calvin.edu/cygwin/release/gettext/gettext-devel/ gettext-devel] package from the [http://www.cygwin.com/ Cygwin] project. Unpack the archive so that everything is under /usr/local instead of /usr. Note that any binaries that are not from the MinGW project or built specially for MSYS cannot be placed in the /msys/1.0/bin (/bin and /usr/bin inside MSYS) directory. You then need to hack the /usr/local/bin/autopoint script so that prefix is defined as /usr/local instead of /usr. Warning - ugly hack follows - Autopoint expects to find an archive.tar.gz in usr/share, so copy gettext (found on usr/share/ on the archive) file structure to /usr/share also.

Update: 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)

and 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]===
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]===
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.28-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.3.4-10-Q16-windows-dll.exe (6.9 Mb)

[link broken as of 9/9/08 - 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

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)

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 <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.

Doc:How Do I

2009-01-08T13:44:16Z

Creek23: /* How to change shortcut keys? */ added Mac

[[Category:Tutorials]]

Feel free to add your own questions here or [[Contact|contact]] us with them. Or put them on the [[Wiki Wish List]].

__TOC__

== Insert some text? ==

With recent development versions, there is a text tool. If you are using 0.61.08 or earlier, use right click on your canvas and choose Layer > New > Other > Text.

== How to change shortcut keys? ==
'''1.''' Find your Synfig config file under:
'''Ubuntu (and other GNU/Linux):''' /home/{username}/.synfig/
'''Mac OS:''' /Users/{username}/Library/Synfig/
'''Windows XP:''' C:\Documents and Settings\{username}\Synfig\
'''Windows Vista:''' C:\Users\{username}\Synfig\
'''2.''' Open the file, named '''accelrc''', using any text editing software (GEdit, Kate, Notepad).

'''3.''' Change the shorcuts you want, save and close.

== How to have a Flash-like shortcut keys? ==
'''1.''' Follow the step on [[Tips#How_to_change_shortcut_keys.3F|how to change shortcut keys]], except for step 3.

'''2.''' Copy the code below and paste it on the very last part of '''accelrc''' then save and close it.
<code>
; misc
(gtk_accel_path "<Actions>//redo" "<Control>y")
; tools
(gtk_accel_path "<Actions>//state-text" "t")
(gtk_accel_path "<Actions>//state-rectangle" "r")
(gtk_accel_path "<Actions>//state-rotate" "<Shift>q")
(gtk_accel_path "<Actions>//state-zoom" "z")
(gtk_accel_path "<Actions>//state-polygon" "n")
(gtk_accel_path "<Actions>//state-bline" "p")
(gtk_accel_path "<Actions>//state-normal" "v")
(gtk_accel_path "<Actions>//state-eyedrop" "i")
(gtk_accel_path "<Actions>//state-fill" "k")
(gtk_accel_path "<Actions>//state-circle" "o")
(gtk_accel_path "<Actions>//state-scale" "q")
(gtk_accel_path "<Actions>//state-gradient" "g")
(gtk_accel_path "<Actions>//state-draw" "y")
; navigation
(gtk_accel_path "<Actions>//seek-next-frame" "period")
(gtk_accel_path "<Actions>//seek-prev-frame" "comma")
</code>

== Apply a gradient to an object instead of the entire canvas? ==

# Create the region you want to fill with a gradient, and the gradient layer, if you haven't already.
# Make sure that the gradient layer is above the region layer in the [[Layers Panel]].
# Select both layers, right click, and select [[Encapsulate]].
# Expand the new [[Paste Canvas|Inline Canvas]] layer if it's not already, and select your gradient layer.
# In the [[Params Panel]] select the [[Blend Method]] parameter, and choose [[Blend Method#Onto|Onto]] from the drop-down menu.

The gradient will clip to the visible area of the region below it inside the [[Paste Canvas|Inline Canvas]]. (and any other layers in that section).

== Show or hide a layer, or fade the effect of a blur? ==
In the [[Params Panel]], look for an option labeled [[Amount Parameter|Amount]] - this controls how much of the blended result of the layer is composited with the blend of the layers beneath it.

In other words, for a typical layer, this will 'fade it out'. For a [[Blur Layer]] set to "[[Blend Method#Straight|Straight]]", this will fade ''between'' the blurred version and the unblurred version of the canvas. If you want it to become less blurry, adjust the [[Blur Layer#Size|Blur Layer's 'size' parameter]].

== Fill an outline? ==
(Requested by [[User:Karlb|Karlb]])

There are several options:
* The easiest way is to link a new region layer to the outline's shape.
*# Select the outline you want to fill.
*# In the Params Panel, right-click the Vertices parameter, select "Export", enter a name for the shape, and hit return. This will export the shape of the outline, making it visible in the Children dialog.
*# In the Children dialog, open the ValueBase Nodes tree and select the name you just saved the shape as.
*# From the [[Layer Menu]] (either context-click on the [[Layers Panel]] or use the [[Canvas Menu Caret]]) create a new [[Region Layer]] by selecting "New Layer -> Geometry -> Region". Ensure that the created layer is selected.
*# In the parameter dialog, right-click the Vertices parameter and click "Connect".
*# Now, if you don't need exported shape, you can unexport it: right click name of the shape in the Children dialog and click "Unexport".
* Similar to the above, but using a different method:
*# Create a new region layer as above, and leave it selected.
*# Don't make any changes to the outline layer, which you want to fill! (see the Tier 5 on the [[Linking]] page for details).
*# Select both layers in the [[Layers Panel]] This will display only the parameters shared by both layers in the [[Params Panel]].
*# Context-click on the [[Vertices Parameter]], and select [[Linking|Link]].
*# The [[Region Layer]] will snap to the shape of the [[Outline Layer]].
* When you create an [[Outline Layer|outline]] with the [[Bline Tool]] that you intend to be a filled area as well, make sure you select the Fill checkbox in the [[Bline Tool#Options|tool options dialog]]. Obviously, this doesn't help much if you realise later that you needed a fill here.
* If you are using the [[draw tool]], there is a button at the bottom of the [[draw tool#Options|tool options dialog]] labeled "Fill Last Stroke", which creates a new [[Region Layer]] and links its shape to the previously drawn outline. Unfortunately, it doesn't work as of Synfig Studio v0.61.04. It has been fixed in the current SVN version of the code.
* Create a [[Region Layer|region]] with the same number of ducks, and manually link each duck. If you want a region that depends on multiple outline layers, this is really your only choice for now.
* Use the draw tool, select only the outline to fill, draw a stroke roughly following the outline and make sure you're holding the Control key when you left go of the mouse button at the end of the stroke. This doesn't work 100% right at the moment.

== Dock windows together? ==

*To dock (join) separate windows into one you must drag the tab ''icons'' for each of the tools into another window.
*You can create subdivisions inside the windows by dragging the icons into the side tabs (located around the edges, the look like rectangles).
*Tool tabs inside the window can be arranged by dragging them on top of one another, therefore changing the order.
*''How Do I min/maximize all Synfig windows on a Windows pc''? There must be an easy way/tool to do this?

== Use an external bitmap? ==

* In the image menu (>) choose file-->import. PNG with alpha channel works fine.
* To animate it without accidental stretching, right-click on the layer and choose encapsulate. You can then animate the position of the new "Inline Canvas" layer instead of the bbox.

== Use an image as a fill colour? ==

Make a new object (bline, region, squares, circles, polygons all work)
Import the image you want as the fill colour, and put it on the layer underneith your object. Set the blend method of the image (using the [[Parameters Palette]]) to "onto" or "straightonto".
Encapsulate the object and the fill colour image, otherwise everthing below the image will have the same fill colour.
Be sure to have a look at what the other composite options do as well.

== Use an external Vector? ==

Synfig doesn't yet support vector import because no-one has written an import process yet. You can use the Svg2synfig [[Converters|converter]], or import it as a bitmap and trace over it in synfig. If you want to implement vector import we would gladly accept your patch.

== Close a bline? ==

* Right click on the starting point and then click on loop bline.

Note: It doesn't work unless the initial point has a tangent - ie the first segment is curved. But you can hide tangent ducks (Alt+3, or "Caret Menu > View > Show/Hide Ducks > Show tangent ducks") and process as described. Don't forget to press (Alt+3) after that to show tangent ducks again.

== How do I transform encapsulated objects? ==

* Right click on the Encapsulated object in the Layer dialog and choose "select all child layers". Then you select the ducks you want to transform (usually just all of them, like for rotating the object), and the rotate or scale tool and do the work.

== Make objects go behind each other, without moving layers? ==

You'll notice each layer you make has a number in the z depth column in the Layers Panel. Say you have 3 layers, they will be numbered 2 (lowest, e.g. a square) 1 (eg a circle) 0 (highest, the default, e.g. a line). In order to make layer 1, the circle, pass behind layer 2, the square, change its z depth to be 3 or more. The z depth of the circle needs to be greater than 2 in order to be behind the square. To make the square on top of everything, you'd change its z depth to -1 or less.

Positive numbers on the z axis go into the screen, and negative numbers go out of the screen, towards the viewer.

It is possible to animate this effect, but each layer is discrete. They seem to go from 0 to 0.9999.

In addition, objects in encapsulated layers can only go behind other objects in the same encapsulated layer. However an encapsulated layer can go behind another encapsulated layer.

== Copy a complex convert combination between parameters of different layers? ==

For example: you want to copy a complicated [[Convert|conversion]] type that you have in one parameter from a layer, to other parameter (maybe not a root parameter, but a sub-parameter) of other layer. If you [[Export|export]] the complicated conversion type from the original layer and then go to the other layer and select [[Connect]] (right click and the exported and the parameter both selected) then you have the parameter form the second layer to be exactly the same than the original one. But there is a drawback: if you modify one of the sub-parameters in the complicated conversion type (e.g. you change the value of one of them) then automatically the same sub-parameter of the other layer is changed.

How can you copy the conversion but allow modify the sub-parameters independently on each layer?

Once you have achieved the complex conversion type in the original layer, don't export the root parameter! If you have done yet [[Export|unexport]] it. (Why?. You will understand it later.) Now duplicate the original layer. Then you should obtain the same layer with the same conversion type placed at the same parameter (but not exported). NOW export the parameter from the duplicated layer. Then go to the (sub) parameter of the layer where you want to copy the complex conversion type and Connect it to the just exported parameter form the duplicated layer. Now delete the duplicated layer (!). Then the exported [[ValueNode]] still undeleted and the layer where you wanted to copy the complex convert type have a (sub) parameter connected to it. You can [[Export|unexport]] the ValueNode or not. It is up to you. But notice that the conversion type is already copied into other (sub) parameter of other layer and they are independent as well as you can change one of them (by modifying the sub-parameters) and the other remains untouched.

== Make an existing animation run at half speed? ==

If you have an animation that runs from 0s to 10s and you want it to run at half speed from 0s to 20s, how can you do that?

* Either: encapsulate it, and use the 'time offset' parameter in the encapsulation layer to slow it down:
** Right-click 'time offset' in the encapsulation layer, convert>linear, rate -0.5 offset 0. That means offset the time by -0.5 seconds per second - or in other words, run at half speed
** Or, putting waypoints on the 'time offset' param would work too: 0 at 0s and -10 at 20s. (The choice between using a linear convert and valuenodes is entirely up to you. They both achieve the same result in this simple case).

* Or: use a [[Time Loop Layer]]. The first method seems better and more intuitive in this case, but there are ways of getting the same effect from the Time Loop layer. Perhaps the Time Loop layer is better if the animation doesn't run from 0s, but from some other time. Anyway: put a Time Loop layer over the layers you wish to slow down, and:
** Either: set duration to 0, local time to 0, convert->linear the link time and set rate to 0.5 - this slows the animation down *to* 50% of its original speed; use bigger rates to slow it down less
** Or: set duration to 1h (*), link time to 0, convert->linear the local time and set rate to 0.5 - this slows the animation down *by* 50%; use bigger rates to slow it down more
(*) if your animation is longer than 1h then set this parameter to EOT (End Of Time) what is the same as Infinite (INF) for a real number but for a time parameter.

== Draw a rectangle with a given width and height? ==

I was asked on IRC how to specify the width and height of a rectangle, rather than having to specify the position of two opposite corners. Here's how:

* draw a rectangle
* go to the [[Params Panel]]
* right-click the 'point 1' parameter and [[Export]]
* give it a name, "p1" say
* right-click the 'point 2' parameter and [[Convert]] to [[Convert#Add|Add]]
* (that's saying that rather than specifying the absolute position of the other point, you want synfig to calculate it for you)
* (it will make 2 new sub-parameters for 'point 2', and the value used for point 2 will be their sum so we want to tell it to use 'point 1' and your (width,height))
* open up the sub-parameters of 'point 2' by clicking the triangle to its left
* go to the [[Children Panel]], open up the values and select the one you exported earlier (p1)
* right-click the "LHS" parameter in the parameters dialog and [[Connect]] it
* then enter the width and height you want in the 'RHS' parameter

== Make linked BLine vertices not affected by Rotate layer? ==
Look at the http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-02-07.log
See also: [[Convert]].

== Create dashed outlines? ==

If you want to make simple dashed outlines the faster way is proceed like this:

* Create a Curve Gradient and an Outline over the same [[Bline]] using the [[Bline Tool]] options. Check both Outline and Gradient at the [[Tool Options Panel]].
* Raise up the gradient layer (it is created below the [[Outline Layer]]).
* Modify the gradient [[Blend Method]] parameter to be Straight Onto. That would render the gradient onto the outline width. Also it wouldn't render the outline, so transparent portions of the gradient are transparent.
* Check the 'Perpendicular' parameter of the Curve Gradient Layer.
* [[Convert]] the Gradient Parameter of the Curve Gradient Layer to be one of those types: Stripes or Repeat Gradient.
* Modify the properties of the sub parameters to achieve the desired effect.

== Render to AVI with higher quality? ==

=== Using raw video ===
The module used by Synfig to render AVI files is ffmpeg. For the moment there is not interface to control ffmpeg options so you render with a fixed bitrate and quality. If you want the maximum quality in your AVI file, follow these steps:

* Render your animation to yuv420p format. To do that select that target at the drop down list of the render dialog and add the ".yuv" extension to your animation name (without quotes).
* Once rendered (it would produce a huge size yuv file) you can quickly convert it to AVI using this command:

ffmpeg -i animation.yuv -sameq animation.avi

Change the animation file name to your one.

=== Rendering trough png sequence. ===
Render your sif to png sequence
mkdir render
synfig my_animation.sifz -o render/frame.png
Then convert it to movie with ffmpeg
ffmpeg -r <frame rate> -i render/frame.%04d.png <more settings from ffmpeg's manual> my_animation.mov
If you need nice open source format without any tweaks you may try ffmpeg2theora:
ffmpeg2theora render/frame.%04d.png --inputfps <frame rate> -o my_animation.ogg
png takes less disk space then yuv.
--[[User:AkhIL|AkhIL]] 21:38, 9 April 2008 (EDT)

==Increase performance by optimizing during compilation time? ==

I would like to know what parameters do I need to apply to configure to improve performance. [[User:Genete|Genete]] 11:04, 9 April 2008 (EDT)

To optimize program you should set two environment variables
export CFLAGS=""
export CXXFLAGS=$CFLAGS

First flag will be "-O3" (ow three). "-02" is normal optimization. "-03" is hard optimisation.

Now you should get info about your CPU
cat /proc/cpuinfo

find your cpu model name

now go to man gcc and searc "-mtune"

find your cpu and add "-mtune=your-cpu -march=your-cpu" to CFLAGS.

Then look at flags from /proc/cpuinfo and search it in gcc manual
For example I have 3dnow. So I can find "-m3dnow". For sse I can find "-msse" and "-mfpmath=sse" (can make program unstable).

Finaly you may add "-ffast-math" to disable math checks. But it can make program unstable.

For my AthlonXP I'm using this flags:
export CFLAGS="-O3 -pipe -mtune=athlon-xp -march=athlon-xp -mmmx -msse -m3dnow -mfpmath=sse -ffast-math -funsigned-char -fno-strict-aliasing"
export CXXFLAGS=$CFLAGS
--[[User:AkhIL|AkhIL]] 12:05, 9 April 2008 (EDT)

For my Pentium3 i use the line:
export CFLAGS="-O3 -pipe -mtune=pentium3 -march=pentium3 -msse -mfpmath=sse -funsigned-char -fno-strict-aliasing"
export CXXFLAGS=$CFLAGS

The additional switches -mmmx and -ffast-math does seem to '''not''' yield any gain in computing performance! So you could leave them out.
--[[User:SvH|SvH]] 03:46, 20 May 2008 (EDT)

== Import a movie into Synfig? ==

To import a movie (image only, not sound) into synfig there is only one option for the moment: Extract an image sequence from the movie and import them using [[ListImporter]]. Before you can load the image sequence you have to extract it from the movie. There are several software to do that but a straight and easy way is to use mplayer:

mplayer mymovie.avi -vo png:z=1 -ss seconds-start -endpos duration

where ''seconds-start'' are the seconds where you want to extract form and ''duration'' is the number of seconds you want to extract from ''mymovie.avi''. Also the image format specified in this case is png but jpeg or tga can be used also. See [http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html mplayer manual page] for more info.

It would extract a set of files of the selected section of the movie. Each file takes the frame number padded with leading zeros as name.

To put all the filenames into a ''.lst'' file just type this in the folder wehre the files are:

ls *.png >> mymovie.lst

and add a line specifying the frame rate at the beginning of the text file:

FPS 25

if the movie was 25 fps.

== Granted Wishes ==

=== MNG target filetype ===

The ability to save as/in the Free/Open MNG (.mng) format [http://libpng.org/pub/mng/]

A partial implementation was committed in SVN r470.

It was implemented in svn 986. See [[Render options]]. --[[User:Genete|Genete]] 13:12, 29 October 2007 (EDT)

=== Optionally display RGB in Hex in Color dialog ===

(3) When colors are quoted as 3 bytes of hexadecimal, you have to convert them to decimal, divide by 255, multiply by 100 to get a number to type into the dialog box. It's painful to match color schemes for example, with the [http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines Tango Icon Theme style guidelines]. [[User:pxegeek|PXEGeek]] 3/16/07

: Added in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=40dda9d27b5249ee32f62d84c819ff569f078929 svn r354]. You can type 3 or 6 digit hex codes and hit return to use. 3 digit code 36a gives colour 3366aa (each digit is duplicated) -- [[User:Dooglus|dooglus]] 3/18/07

:: Many thanks - already used many times! PXEGeek.

::: Did you notice that you can use single digit codes too? '5' gives 555555 for instance, giving you 16 equally spaces shades of black through white. -- [[User:Dooglus|dooglus]] 17:51, 25 September 2007 (EDT)

=== Restore Default Layout ===

(3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.
-> I'd like to second this one - especially with the bug where dialog boxes sometime shrink to nothing or offscreen, and no amount of maximizing or minimizing restores them. The only solution is to kill the windows, and none of the combo options in the dialog menu match the default configuration. 4/4/07 PXEGeek

: Implemented in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=036306f3c2c265a604971728d50fcce258766552 svn r757] -- [[User:Dooglus|dooglus]] 17:48, 25 September 2007 (EDT)

=== General outline / Polygon-based Outline / "Set Tangents to Zero" button ===
(3.5) I'm no artist, thus my primary form of art is stick figures, not to mention, many interesting animations are done in stick-figure style. Stick figures must be perfectly straight to get the effect across, so when I'm making an outline using B-Curves, it is too time consuming to set the tangents to 0 each time. Similarly, outlines of other shapes like squares, circles and so forth would be very useful. Whichever of the above is easiest, please implement right away. --[[User:Dragontamer|Dragontamer]] 02:35, 19 November 2007 (EST)
: For perfectly straight lines, click without moving the mouse. You will get a single point with no tangents. Outline shapes would require some development, particularly with some thought given to backward compatibility. A workaround you might consider is to create a duplicate shape with a different color and make the top one slightly smaller, so the outline of the one below shows. [[User:Pxegeek|Pxegeek]] 21:58, 19 November 2007 (EST)
:: Well, in general, whenever I click on a point to edit it (say, to make it move somewhere in animation mode), there is a decent chance that I click on a tangent instead. Then, if I want to right click the point itself, I usually right click the tangent marker instead. It isn't that big a deal, but simplicity at the cost of power generally is a good thing, especially when it will save a few mouse clicks.
:: As for the outlines, yeah, I've tried that and it is a decent solution for now, although it is no replacement for a real outline. I am going to also experiment with a clamp to see if I can make the center of the shape have 100% alpha... but I don't have synfig on the computer I'm on right now. Thanks for the tips Pxegeek. --[[User:Dragontamer|Dragontamer]] 01:58, 27 November 2007 (EST)
::: You can press Alt+3 to hide tangent ducks. --[[User:Zelgadis|Zelgadis]] 09:27, 27 November 2007 (EST)

=== Copy & Paste/Image Importing ===

(4) I sometimes make graphics in other programs, or use clipart and other images. Would it be possible for Synfig to be able to import images and/or copy and paste them?--Khlieeq 2007-07-19
Well, it doesn't support Copy & paste from the clipboard, but you can import images using "New Layer -> Other -> Import". This will create an Import layer, for which you can then edit the properties to point to the file containing your image. PXEGeek. 2007-07-19

=== Recursive Waypoint Manipulation ===

(4) it is really tiresome to revert changes to waypoints created by manipulating tangent/position ducks or change their interpolation functions. making it possible to right-click-modify the waypoint shown for objects that have some waypoint in a referenced sub-object would be great! -- timonator 2007-06-01
:You can do it in two ways: changing the interpolation method of the waypoint of paste canvas or editing the keyframe properties. The first allow to modify the waypoints interpolation method for all the waypoints of all the parameters of all the layers that are inside the paste canvas layer. You can right click on the left or right part of the waypoint to edit by a context menu the left or the right interpolation method of the waipoints. The second method would add and modify all the parameters that have any waypoint in the animation. See [[Keyframe]] for more detail. --[[User:Genete|Genete]] 13:10, 29 October 2007 (EDT)

=== Tweening for images developed in other imaging programs ===

It's obvious I am a beginner at image movement, but morphing is not enough: movement across the page is needed. Thanks for listening. [[User:Comwell@bellsouth.net|Comwell]] 
Imported images can be moved across the page. They can also be scaled, rotated and deformed. Was there a specific example you had in mind? [[User:Pxegeek|pxegeek]] 
:I also would like a way to tween images that have been drawn in other programs. I've had trouble drawing with Bline tool and the drawing tool in Synfig, and I'd rather just draw with a paint brush (like the one in Photoshop). Another problem I have is that Synfig tends to shut down on me every 20 minutes or so, and it's really frustrating even with the auto recover feature, because my sketches disappear. It'd be nice if I'm able to draw all of the keyframes in Photoshop or another image program and import it to Synfig so that Synfig can tween and animate them. Thank you. [[User:xychefoo@gmail.com|Huina]]
::You CAN use images, drawn in other programs. Just select "File->Import" from [[Canvas Menu Caret|canvas menu]] --[[User:Zelgadis|Zelgadis]] 01:39, 24 November 2007 (EST)
:::But how do you animate using images from other sources? I tried to make 2 keyframes with 2 different images, and it doesn't animate. It just stays as 1 picture for the entire render. The closest thing I saw to importing images from another source into Synfig and having it animate is the Walking Cycle Tutorial, but I would still have to trace the images to make it animate. As I said earlier, I'm not entirely fond of using the draw/Bline tool. [[User:xychefoo@gmail.com|Huina]]
:::: Huina, there's no way to do what you want right now. Interpolating between two images that are not created in Synfig is well beyond its scope right now. However, what you could do is take an image and separate elements of the picture onto different layers (e.g. have a picture of an arm and another of the rest of the body) and you can move those around, stretch and rotate them. (If you're familiar with the work of Terry Gilliam on Monty Python you'll know what I mean) I don't know how feasible it is to implement your request (I suspect some heavy lifting). We'll keep it on the list, but don't hold your breath. [[User:Pxegeek|Pxegeek]] 19:57, 24 November 2007 (EST)

:::: I think, you hardly find any other animation package which allow you to do such things. You could use a special tools for this task, like xmorph (http://xmorph.sourceforge.net/). But to do the tween between two bitmap images you STILL need to set points. It's not tracing, but very similar. Anyway, result may be poor and I'd better suggest to use technique, described in Walking Cycle Tutorial or which the [[User:Pxegeek|Pxegeek]] meant. --[[User:Zelgadis|Zelgadis]] 02:08, 25 November 2007 (EST)

:::: There is a technique called "optical flow". It takes two input frames and calculates the movement of each individual pixel between the frames, allowing interpolation to be done. Here's an example: http://www.fxguide.com/article333.html. It doesn't require setting of control points, but it has problems it's own set of problems: http://www.fxguide.com/article333.html. --[[User:Yoyobuae|Yoyobuae]] 13:32, 3 February 2008 (EST)

=== Auto-link option in [[Draw tool]] ===

(4) so that you can draw a line, and have its endpoint automatically link to a duck - or if Auto-connect is off, you can get a line object linked to the end of another line object. / I missed this too, it even should be like that by default I think. [[User:Maxy|Maxy]] 13:22, 25 Apr 2006 (PDT)

: Isn't this done already? We don't have line objects, but blines are automatically linked to if auto-connect is on. Am I missing something? -- [[User:Dooglus|dooglus]] 17:29, 27 September 2007 (EDT)

::To clarify dooglus' comments - If you have an outline created by the draw tool highlighted in the layer dialog and the auto-extend checkbox is checked, then you can continue drawing with the draw tool in that same layer. Blines created with the Bline tool cannot be extended once a different tool or layer is selected. [[User:Pxegeek|Pxegeek]] 23:46, 12 October 2007 (EDT)

::: A line is a line - Synfig doesn't remember whether it was created with the Bline tool or the Draw tool - so you can extend blines created with the bline tool using the draw tool. Just make sure the line is selected (so that its ducks are visible), not looped (so that it has end points to extend from), enable the draw tool, check 'auto extend' and start drawing at one of its end ducks. [[User:Dooglus|dooglus]] 05:47, 13 October 2007 (EDT)

So this sounds like it is already done. But on a related note, being able to open an existing bline in the bline tool to extend it would be useful. -- [[User:Dooglus|dooglus]] 04:51, 29 January 2008 (EST)

=== Layer hide boolean parameter ===

(3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Panel]], and builds upon it as well, allowing the [[Layers Panel]] to dynamically unclutter. ''(This feature request is a refactoring of the [[Amount Parameter]])''
: With the addition of the [[Convert#Switch|Switch]] type conversion it is not needed this feature request. You can convert the Amount parameter to a Switch value and give 0 and 1 to the Linked OFF/ON values. --[[User:Genete|Genete]] 13:20, 29 October 2007 (EDT)

=== Riding ducks ===

(2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.
:Already done in SVN.[[User:Genete|Genete]] 18:59, 5 April 2008 (EDT)

=== Image filmstrip import ===

(2) — Allow import of a series of images (TGA, etc) as frames of an animation, on a layer. 
Response - 'lst' files of a list of images can be imported. I've used this to develop a walk cycle. See [[Walk_Cycle|Walk cycle]] for an example. [[user:pxegeek|pxegeek]]

=== Character Animation Tools ===

I have seen some interesting methods for helping character design/animation in different 2d/3d software. Hash's animation master has 'poses' which are extremes of a model, for example smiling and frowning, once you add these extremes ot a set you can use slider to create a pose that somewhere inbetween. The real power of this is when you have serveral different poses on the same object, a face say, you can easily come up with new facial expressions. Maybe something similar could be done with synfig using layers and groups, the implementation could something similar to Moho's switch layers. --[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)
: Have you read this tutorial? [[Reuse Animations]]. It is very close to the Switch layer of Moho/Anime Studio. Also You can change the Canvas parameter to any other canvas dynamically in the time line by clicking on it and selecting other exported canvas. Other option is convert the canvas to a Switch type and alternate between two different canvas. --[[User:Genete|Genete]] 13:26, 29 October 2007 (EDT)

=== More Animation Tools ===

[[New Animation Tools|Added here]]

=== Improved User Experience for First Contact ===
* Single file download and installer (at least for Windows)
* Ability to draw the first object directly after starting the application (start with an empty document)
* Ability to animate the object directly after drawing the first object (new documents have a say 3 seconds timeline)
In my opinion this is crucial to attract potential users. Because if I see how easy it is to create my first animation I'm going to accept all the bugs and clumsyness. A good example is the Pencil animation software. --[[User:Dmd|Dmd]] 13:50, 26 January 2008 (EST)

: I've implemented #2 and #3 above in svn r1519 & 1520. If no files are specified to be opened when running studio, it'll make a new one. It won't pop up the canvas properties dialog when making new canvases by default. And the default end time is 5s (3s is small enough to cause the time slider to show "1s 12f", whereas 5s looks cleaner). -- [[User:Dooglus|dooglus]] 04:00, 29 January 2008 (EST)

=== Automatic attach and manipulate a Vertex to a Bline ===

Please see [[Inverse Duck Manipulation|this]] page to understand what we want. --[[User:Genete|Genete]] 12:43, 3 March 2008 (EST).
:Already done in SVN. [[User:Genete|Genete]] 19:00, 5 April 2008 (EDT)

=== Toggle visible ducks ===
(3) So pressing, say, tab while editing a Bline toggles which vertices/ducks are visible - so we can easily move the actual vertices around without having the view cluttered by tangeants (and also make it easier to select 'Loop' rather than 'Split Tangeants' when creating the thing.)

Given that extra ducks such as the width ones listed above may be added, this might become more and more necessary. If too many different sets are added for toggling to be feasible, each visibility for each set can be hotkeyed.

: Synfig already have hotkeys to toggle visibility of the ducks. See [[Keyboard_Shortcuts#Hotkeys_Visual_Guide]]. --[[User:Zelgadis|Zelgadis]] 00:39, 22 April 2008 (EDT)

Keyboard Shortcuts (Flash)

2009-01-08T05:12:16Z

Creek23: /* How to have a Flash-like shortcut keys in Synfig? */ added Draw

=== How to have a Flash-like shortcut keys in Synfig? ===
This is how you can make a Flash-like shortcut keys in Synfig.

'''NOTE:''' You must have Synfig installed and run at least once. :D

'''1.''' Find your Synfig config file under:
''Ubuntu GNU/Linux:'' /home/{username}/.synfig/
''Windows XP:'' C:\Documents and Settings\{username}\Synfig\
''Windows Vista:'' C:\Users\{username}\Synfig\
'''2.''' Open the file, named '''accelrc''', using any text editing software (GEdit, Kate, Notepad).

'''3.''' Copy the code below and paste it on the very last part of '''accelrc'''.
<code>
; misc
(gtk_accel_path "<Actions>//redo" "<Control>y")
; tools
(gtk_accel_path "<Actions>//state-text" "t")
(gtk_accel_path "<Actions>//state-rectangle" "r")
(gtk_accel_path "<Actions>//state-rotate" "<Shift>q")
(gtk_accel_path "<Actions>//state-zoom" "z")
(gtk_accel_path "<Actions>//state-polygon" "n")
(gtk_accel_path "<Actions>//state-bline" "p")
(gtk_accel_path "<Actions>//state-normal" "v")
(gtk_accel_path "<Actions>//state-eyedrop" "i")
(gtk_accel_path "<Actions>//state-fill" "k")
(gtk_accel_path "<Actions>//state-circle" "o")
(gtk_accel_path "<Actions>//state-scale" "q")
(gtk_accel_path "<Actions>//state-gradient" "g")
(gtk_accel_path "<Actions>//state-draw" "y")
; navigation
(gtk_accel_path "<Actions>//seek-next-frame" "period")
(gtk_accel_path "<Actions>//seek-prev-frame" "comma")
</code>
'''4.''' Save it, and run Synfig to test and enjoy!

=== How to restore to default settings? ===
Simply, delete '''accelrc''' and run Synfig.

Doc:How Do I

2009-01-08T05:10:13Z

Creek23: /* How to have a Flash-like shortcut keys? */ added Draw

[[Category:Tutorials]]

Feel free to add your own questions here or [[Contact|contact]] us with them. Or put them on the [[Wiki Wish List]].

__TOC__

== Insert some text? ==

With recent development versions, there is a text tool. If you are using 0.61.08 or earlier, use right click on your canvas and choose Layer > New > Other > Text.

== How to change shortcut keys? ==
'''1.''' Find your Synfig config file under:
''Ubuntu GNU/Linux:'' /home/{username}/Synfig/
''Windows XP:'' C:\Documents and Settings\{username}\Synfig\
''Windows Vista:'' C:\Users\{username}\Synfig\
'''2.''' Open the file, named '''accelrc''', using any text editing software (GEdit, Kate, Notepad).

'''3.''' Change the shorcuts you want, save and close.

== How to have a Flash-like shortcut keys? ==
'''1.''' Follow the step on [[Tips#How_to_change_shortcut_keys.3F|how to change shortcut keys]], except for step 3.

'''2.''' Copy the code below and paste it on the very last part of '''accelrc''' then save and close it.
<code>
; misc
(gtk_accel_path "<Actions>//redo" "<Control>y")
; tools
(gtk_accel_path "<Actions>//state-text" "t")
(gtk_accel_path "<Actions>//state-rectangle" "r")
(gtk_accel_path "<Actions>//state-rotate" "<Shift>q")
(gtk_accel_path "<Actions>//state-zoom" "z")
(gtk_accel_path "<Actions>//state-polygon" "n")
(gtk_accel_path "<Actions>//state-bline" "p")
(gtk_accel_path "<Actions>//state-normal" "v")
(gtk_accel_path "<Actions>//state-eyedrop" "i")
(gtk_accel_path "<Actions>//state-fill" "k")
(gtk_accel_path "<Actions>//state-circle" "o")
(gtk_accel_path "<Actions>//state-scale" "q")
(gtk_accel_path "<Actions>//state-gradient" "g")
(gtk_accel_path "<Actions>//state-draw" "y")
; navigation
(gtk_accel_path "<Actions>//seek-next-frame" "period")
(gtk_accel_path "<Actions>//seek-prev-frame" "comma")
</code>

== Apply a gradient to an object instead of the entire canvas? ==

# Create the region you want to fill with a gradient, and the gradient layer, if you haven't already.
# Make sure that the gradient layer is above the region layer in the [[Layers Panel]].
# Select both layers, right click, and select [[Encapsulate]].
# Expand the new [[Paste Canvas|Inline Canvas]] layer if it's not already, and select your gradient layer.
# In the [[Params Panel]] select the [[Blend Method]] parameter, and choose [[Blend Method#Onto|Onto]] from the drop-down menu.

The gradient will clip to the visible area of the region below it inside the [[Paste Canvas|Inline Canvas]]. (and any other layers in that section).

== Show or hide a layer, or fade the effect of a blur? ==
In the [[Params Panel]], look for an option labeled [[Amount Parameter|Amount]] - this controls how much of the blended result of the layer is composited with the blend of the layers beneath it.

In other words, for a typical layer, this will 'fade it out'. For a [[Blur Layer]] set to "[[Blend Method#Straight|Straight]]", this will fade ''between'' the blurred version and the unblurred version of the canvas. If you want it to become less blurry, adjust the [[Blur Layer#Size|Blur Layer's 'size' parameter]].

== Fill an outline? ==
(Requested by [[User:Karlb|Karlb]])

There are several options:
* The easiest way is to link a new region layer to the outline's shape.
*# Select the outline you want to fill.
*# In the Params Panel, right-click the Vertices parameter, select "Export", enter a name for the shape, and hit return. This will export the shape of the outline, making it visible in the Children dialog.
*# In the Children dialog, open the ValueBase Nodes tree and select the name you just saved the shape as.
*# From the [[Layer Menu]] (either context-click on the [[Layers Panel]] or use the [[Canvas Menu Caret]]) create a new [[Region Layer]] by selecting "New Layer -> Geometry -> Region". Ensure that the created layer is selected.
*# In the parameter dialog, right-click the Vertices parameter and click "Connect".
*# Now, if you don't need exported shape, you can unexport it: right click name of the shape in the Children dialog and click "Unexport".
* Similar to the above, but using a different method:
*# Create a new region layer as above, and leave it selected.
*# Don't make any changes to the outline layer, which you want to fill! (see the Tier 5 on the [[Linking]] page for details).
*# Select both layers in the [[Layers Panel]] This will display only the parameters shared by both layers in the [[Params Panel]].
*# Context-click on the [[Vertices Parameter]], and select [[Linking|Link]].
*# The [[Region Layer]] will snap to the shape of the [[Outline Layer]].
* When you create an [[Outline Layer|outline]] with the [[Bline Tool]] that you intend to be a filled area as well, make sure you select the Fill checkbox in the [[Bline Tool#Options|tool options dialog]]. Obviously, this doesn't help much if you realise later that you needed a fill here.
* If you are using the [[draw tool]], there is a button at the bottom of the [[draw tool#Options|tool options dialog]] labeled "Fill Last Stroke", which creates a new [[Region Layer]] and links its shape to the previously drawn outline. Unfortunately, it doesn't work as of Synfig Studio v0.61.04. It has been fixed in the current SVN version of the code.
* Create a [[Region Layer|region]] with the same number of ducks, and manually link each duck. If you want a region that depends on multiple outline layers, this is really your only choice for now.
* Use the draw tool, select only the outline to fill, draw a stroke roughly following the outline and make sure you're holding the Control key when you left go of the mouse button at the end of the stroke. This doesn't work 100% right at the moment.

== Dock windows together? ==

*To dock (join) separate windows into one you must drag the tab ''icons'' for each of the tools into another window.
*You can create subdivisions inside the windows by dragging the icons into the side tabs (located around the edges, the look like rectangles).
*Tool tabs inside the window can be arranged by dragging them on top of one another, therefore changing the order.
*''How Do I min/maximize all Synfig windows on a Windows pc''? There must be an easy way/tool to do this?

== Use an external bitmap? ==

* In the image menu (>) choose file-->import. PNG with alpha channel works fine.
* To animate it without accidental stretching, right-click on the layer and choose encapsulate. You can then animate the position of the new "Inline Canvas" layer instead of the bbox.

== Use an image as a fill colour? ==

Make a new object (bline, region, squares, circles, polygons all work)
Import the image you want as the fill colour, and put it on the layer underneith your object. Set the blend method of the image (using the [[Parameters Palette]]) to "onto" or "straightonto".
Encapsulate the object and the fill colour image, otherwise everthing below the image will have the same fill colour.
Be sure to have a look at what the other composite options do as well.

== Use an external Vector? ==

Synfig doesn't yet support vector import because no-one has written an import process yet. You can use the Svg2synfig [[Converters|converter]], or import it as a bitmap and trace over it in synfig. If you want to implement vector import we would gladly accept your patch.

== Close a bline? ==

* Right click on the starting point and then click on loop bline.

Note: It doesn't work unless the initial point has a tangent - ie the first segment is curved. But you can hide tangent ducks (Alt+3, or "Caret Menu > View > Show/Hide Ducks > Show tangent ducks") and process as described. Don't forget to press (Alt+3) after that to show tangent ducks again.

== How do I transform encapsulated objects? ==

* Right click on the Encapsulated object in the Layer dialog and choose "select all child layers". Then you select the ducks you want to transform (usually just all of them, like for rotating the object), and the rotate or scale tool and do the work.

== Make objects go behind each other, without moving layers? ==

You'll notice each layer you make has a number in the z depth column in the Layers Panel. Say you have 3 layers, they will be numbered 2 (lowest, e.g. a square) 1 (eg a circle) 0 (highest, the default, e.g. a line). In order to make layer 1, the circle, pass behind layer 2, the square, change its z depth to be 3 or more. The z depth of the circle needs to be greater than 2 in order to be behind the square. To make the square on top of everything, you'd change its z depth to -1 or less.

Positive numbers on the z axis go into the screen, and negative numbers go out of the screen, towards the viewer.

It is possible to animate this effect, but each layer is discrete. They seem to go from 0 to 0.9999.

In addition, objects in encapsulated layers can only go behind other objects in the same encapsulated layer. However an encapsulated layer can go behind another encapsulated layer.

== Copy a complex convert combination between parameters of different layers? ==

For example: you want to copy a complicated [[Convert|conversion]] type that you have in one parameter from a layer, to other parameter (maybe not a root parameter, but a sub-parameter) of other layer. If you [[Export|export]] the complicated conversion type from the original layer and then go to the other layer and select [[Connect]] (right click and the exported and the parameter both selected) then you have the parameter form the second layer to be exactly the same than the original one. But there is a drawback: if you modify one of the sub-parameters in the complicated conversion type (e.g. you change the value of one of them) then automatically the same sub-parameter of the other layer is changed.

How can you copy the conversion but allow modify the sub-parameters independently on each layer?

Once you have achieved the complex conversion type in the original layer, don't export the root parameter! If you have done yet [[Export|unexport]] it. (Why?. You will understand it later.) Now duplicate the original layer. Then you should obtain the same layer with the same conversion type placed at the same parameter (but not exported). NOW export the parameter from the duplicated layer. Then go to the (sub) parameter of the layer where you want to copy the complex conversion type and Connect it to the just exported parameter form the duplicated layer. Now delete the duplicated layer (!). Then the exported [[ValueNode]] still undeleted and the layer where you wanted to copy the complex convert type have a (sub) parameter connected to it. You can [[Export|unexport]] the ValueNode or not. It is up to you. But notice that the conversion type is already copied into other (sub) parameter of other layer and they are independent as well as you can change one of them (by modifying the sub-parameters) and the other remains untouched.

== Make an existing animation run at half speed? ==

If you have an animation that runs from 0s to 10s and you want it to run at half speed from 0s to 20s, how can you do that?

* Either: encapsulate it, and use the 'time offset' parameter in the encapsulation layer to slow it down:
** Right-click 'time offset' in the encapsulation layer, convert>linear, rate -0.5 offset 0. That means offset the time by -0.5 seconds per second - or in other words, run at half speed
** Or, putting waypoints on the 'time offset' param would work too: 0 at 0s and -10 at 20s. (The choice between using a linear convert and valuenodes is entirely up to you. They both achieve the same result in this simple case).

* Or: use a [[Time Loop Layer]]. The first method seems better and more intuitive in this case, but there are ways of getting the same effect from the Time Loop layer. Perhaps the Time Loop layer is better if the animation doesn't run from 0s, but from some other time. Anyway: put a Time Loop layer over the layers you wish to slow down, and:
** Either: set duration to 0, local time to 0, convert->linear the link time and set rate to 0.5 - this slows the animation down *to* 50% of its original speed; use bigger rates to slow it down less
** Or: set duration to 1h (*), link time to 0, convert->linear the local time and set rate to 0.5 - this slows the animation down *by* 50%; use bigger rates to slow it down more
(*) if your animation is longer than 1h then set this parameter to EOT (End Of Time) what is the same as Infinite (INF) for a real number but for a time parameter.

== Draw a rectangle with a given width and height? ==

I was asked on IRC how to specify the width and height of a rectangle, rather than having to specify the position of two opposite corners. Here's how:

* draw a rectangle
* go to the [[Params Panel]]
* right-click the 'point 1' parameter and [[Export]]
* give it a name, "p1" say
* right-click the 'point 2' parameter and [[Convert]] to [[Convert#Add|Add]]
* (that's saying that rather than specifying the absolute position of the other point, you want synfig to calculate it for you)
* (it will make 2 new sub-parameters for 'point 2', and the value used for point 2 will be their sum so we want to tell it to use 'point 1' and your (width,height))
* open up the sub-parameters of 'point 2' by clicking the triangle to its left
* go to the [[Children Panel]], open up the values and select the one you exported earlier (p1)
* right-click the "LHS" parameter in the parameters dialog and [[Connect]] it
* then enter the width and height you want in the 'RHS' parameter

== Make linked BLine vertices not affected by Rotate layer? ==
Look at the http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-02-07.log
See also: [[Convert]].

== Create dashed outlines? ==

If you want to make simple dashed outlines the faster way is proceed like this:

* Create a Curve Gradient and an Outline over the same [[Bline]] using the [[Bline Tool]] options. Check both Outline and Gradient at the [[Tool Options Panel]].
* Raise up the gradient layer (it is created below the [[Outline Layer]]).
* Modify the gradient [[Blend Method]] parameter to be Straight Onto. That would render the gradient onto the outline width. Also it wouldn't render the outline, so transparent portions of the gradient are transparent.
* Check the 'Perpendicular' parameter of the Curve Gradient Layer.
* [[Convert]] the Gradient Parameter of the Curve Gradient Layer to be one of those types: Stripes or Repeat Gradient.
* Modify the properties of the sub parameters to achieve the desired effect.

== Render to AVI with higher quality? ==

=== Using raw video ===
The module used by Synfig to render AVI files is ffmpeg. For the moment there is not interface to control ffmpeg options so you render with a fixed bitrate and quality. If you want the maximum quality in your AVI file, follow these steps:

* Render your animation to yuv420p format. To do that select that target at the drop down list of the render dialog and add the ".yuv" extension to your animation name (without quotes).
* Once rendered (it would produce a huge size yuv file) you can quickly convert it to AVI using this command:

ffmpeg -i animation.yuv -sameq animation.avi

Change the animation file name to your one.

=== Rendering trough png sequence. ===
Render your sif to png sequence
mkdir render
synfig my_animation.sifz -o render/frame.png
Then convert it to movie with ffmpeg
ffmpeg -r <frame rate> -i render/frame.%04d.png <more settings from ffmpeg's manual> my_animation.mov
If you need nice open source format without any tweaks you may try ffmpeg2theora:
ffmpeg2theora render/frame.%04d.png --inputfps <frame rate> -o my_animation.ogg
png takes less disk space then yuv.
--[[User:AkhIL|AkhIL]] 21:38, 9 April 2008 (EDT)

==Increase performance by optimizing during compilation time? ==

I would like to know what parameters do I need to apply to configure to improve performance. [[User:Genete|Genete]] 11:04, 9 April 2008 (EDT)

To optimize program you should set two environment variables
export CFLAGS=""
export CXXFLAGS=$CFLAGS

First flag will be "-O3" (ow three). "-02" is normal optimization. "-03" is hard optimisation.

Now you should get info about your CPU
cat /proc/cpuinfo

find your cpu model name

now go to man gcc and searc "-mtune"

find your cpu and add "-mtune=your-cpu -march=your-cpu" to CFLAGS.

Then look at flags from /proc/cpuinfo and search it in gcc manual
For example I have 3dnow. So I can find "-m3dnow". For sse I can find "-msse" and "-mfpmath=sse" (can make program unstable).

Finaly you may add "-ffast-math" to disable math checks. But it can make program unstable.

For my AthlonXP I'm using this flags:
export CFLAGS="-O3 -pipe -mtune=athlon-xp -march=athlon-xp -mmmx -msse -m3dnow -mfpmath=sse -ffast-math -funsigned-char -fno-strict-aliasing"
export CXXFLAGS=$CFLAGS
--[[User:AkhIL|AkhIL]] 12:05, 9 April 2008 (EDT)

For my Pentium3 i use the line:
export CFLAGS="-O3 -pipe -mtune=pentium3 -march=pentium3 -msse -mfpmath=sse -funsigned-char -fno-strict-aliasing"
export CXXFLAGS=$CFLAGS

The additional switches -mmmx and -ffast-math does seem to '''not''' yield any gain in computing performance! So you could leave them out.
--[[User:SvH|SvH]] 03:46, 20 May 2008 (EDT)

== Import a movie into Synfig? ==

To import a movie (image only, not sound) into synfig there is only one option for the moment: Extract an image sequence from the movie and import them using [[ListImporter]]. Before you can load the image sequence you have to extract it from the movie. There are several software to do that but a straight and easy way is to use mplayer:

mplayer mymovie.avi -vo png:z=1 -ss seconds-start -endpos duration

where ''seconds-start'' are the seconds where you want to extract form and ''duration'' is the number of seconds you want to extract from ''mymovie.avi''. Also the image format specified in this case is png but jpeg or tga can be used also. See [http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html mplayer manual page] for more info.

It would extract a set of files of the selected section of the movie. Each file takes the frame number padded with leading zeros as name.

To put all the filenames into a ''.lst'' file just type this in the folder wehre the files are:

ls *.png >> mymovie.lst

and add a line specifying the frame rate at the beginning of the text file:

FPS 25

if the movie was 25 fps.

== Granted Wishes ==

=== MNG target filetype ===

The ability to save as/in the Free/Open MNG (.mng) format [http://libpng.org/pub/mng/]

A partial implementation was committed in SVN r470.

It was implemented in svn 986. See [[Render options]]. --[[User:Genete|Genete]] 13:12, 29 October 2007 (EDT)

=== Optionally display RGB in Hex in Color dialog ===

(3) When colors are quoted as 3 bytes of hexadecimal, you have to convert them to decimal, divide by 255, multiply by 100 to get a number to type into the dialog box. It's painful to match color schemes for example, with the [http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines Tango Icon Theme style guidelines]. [[User:pxegeek|PXEGeek]] 3/16/07

: Added in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=40dda9d27b5249ee32f62d84c819ff569f078929 svn r354]. You can type 3 or 6 digit hex codes and hit return to use. 3 digit code 36a gives colour 3366aa (each digit is duplicated) -- [[User:Dooglus|dooglus]] 3/18/07

:: Many thanks - already used many times! PXEGeek.

::: Did you notice that you can use single digit codes too? '5' gives 555555 for instance, giving you 16 equally spaces shades of black through white. -- [[User:Dooglus|dooglus]] 17:51, 25 September 2007 (EDT)

=== Restore Default Layout ===

(3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.
-> I'd like to second this one - especially with the bug where dialog boxes sometime shrink to nothing or offscreen, and no amount of maximizing or minimizing restores them. The only solution is to kill the windows, and none of the combo options in the dialog menu match the default configuration. 4/4/07 PXEGeek

: Implemented in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=036306f3c2c265a604971728d50fcce258766552 svn r757] -- [[User:Dooglus|dooglus]] 17:48, 25 September 2007 (EDT)

=== General outline / Polygon-based Outline / "Set Tangents to Zero" button ===
(3.5) I'm no artist, thus my primary form of art is stick figures, not to mention, many interesting animations are done in stick-figure style. Stick figures must be perfectly straight to get the effect across, so when I'm making an outline using B-Curves, it is too time consuming to set the tangents to 0 each time. Similarly, outlines of other shapes like squares, circles and so forth would be very useful. Whichever of the above is easiest, please implement right away. --[[User:Dragontamer|Dragontamer]] 02:35, 19 November 2007 (EST)
: For perfectly straight lines, click without moving the mouse. You will get a single point with no tangents. Outline shapes would require some development, particularly with some thought given to backward compatibility. A workaround you might consider is to create a duplicate shape with a different color and make the top one slightly smaller, so the outline of the one below shows. [[User:Pxegeek|Pxegeek]] 21:58, 19 November 2007 (EST)
:: Well, in general, whenever I click on a point to edit it (say, to make it move somewhere in animation mode), there is a decent chance that I click on a tangent instead. Then, if I want to right click the point itself, I usually right click the tangent marker instead. It isn't that big a deal, but simplicity at the cost of power generally is a good thing, especially when it will save a few mouse clicks.
:: As for the outlines, yeah, I've tried that and it is a decent solution for now, although it is no replacement for a real outline. I am going to also experiment with a clamp to see if I can make the center of the shape have 100% alpha... but I don't have synfig on the computer I'm on right now. Thanks for the tips Pxegeek. --[[User:Dragontamer|Dragontamer]] 01:58, 27 November 2007 (EST)
::: You can press Alt+3 to hide tangent ducks. --[[User:Zelgadis|Zelgadis]] 09:27, 27 November 2007 (EST)

=== Copy & Paste/Image Importing ===

(4) I sometimes make graphics in other programs, or use clipart and other images. Would it be possible for Synfig to be able to import images and/or copy and paste them?--Khlieeq 2007-07-19
Well, it doesn't support Copy & paste from the clipboard, but you can import images using "New Layer -> Other -> Import". This will create an Import layer, for which you can then edit the properties to point to the file containing your image. PXEGeek. 2007-07-19

=== Recursive Waypoint Manipulation ===

(4) it is really tiresome to revert changes to waypoints created by manipulating tangent/position ducks or change their interpolation functions. making it possible to right-click-modify the waypoint shown for objects that have some waypoint in a referenced sub-object would be great! -- timonator 2007-06-01
:You can do it in two ways: changing the interpolation method of the waypoint of paste canvas or editing the keyframe properties. The first allow to modify the waypoints interpolation method for all the waypoints of all the parameters of all the layers that are inside the paste canvas layer. You can right click on the left or right part of the waypoint to edit by a context menu the left or the right interpolation method of the waipoints. The second method would add and modify all the parameters that have any waypoint in the animation. See [[Keyframe]] for more detail. --[[User:Genete|Genete]] 13:10, 29 October 2007 (EDT)

=== Tweening for images developed in other imaging programs ===

It's obvious I am a beginner at image movement, but morphing is not enough: movement across the page is needed. Thanks for listening. [[User:Comwell@bellsouth.net|Comwell]] 
Imported images can be moved across the page. They can also be scaled, rotated and deformed. Was there a specific example you had in mind? [[User:Pxegeek|pxegeek]] 
:I also would like a way to tween images that have been drawn in other programs. I've had trouble drawing with Bline tool and the drawing tool in Synfig, and I'd rather just draw with a paint brush (like the one in Photoshop). Another problem I have is that Synfig tends to shut down on me every 20 minutes or so, and it's really frustrating even with the auto recover feature, because my sketches disappear. It'd be nice if I'm able to draw all of the keyframes in Photoshop or another image program and import it to Synfig so that Synfig can tween and animate them. Thank you. [[User:xychefoo@gmail.com|Huina]]
::You CAN use images, drawn in other programs. Just select "File->Import" from [[Canvas Menu Caret|canvas menu]] --[[User:Zelgadis|Zelgadis]] 01:39, 24 November 2007 (EST)
:::But how do you animate using images from other sources? I tried to make 2 keyframes with 2 different images, and it doesn't animate. It just stays as 1 picture for the entire render. The closest thing I saw to importing images from another source into Synfig and having it animate is the Walking Cycle Tutorial, but I would still have to trace the images to make it animate. As I said earlier, I'm not entirely fond of using the draw/Bline tool. [[User:xychefoo@gmail.com|Huina]]
:::: Huina, there's no way to do what you want right now. Interpolating between two images that are not created in Synfig is well beyond its scope right now. However, what you could do is take an image and separate elements of the picture onto different layers (e.g. have a picture of an arm and another of the rest of the body) and you can move those around, stretch and rotate them. (If you're familiar with the work of Terry Gilliam on Monty Python you'll know what I mean) I don't know how feasible it is to implement your request (I suspect some heavy lifting). We'll keep it on the list, but don't hold your breath. [[User:Pxegeek|Pxegeek]] 19:57, 24 November 2007 (EST)

:::: I think, you hardly find any other animation package which allow you to do such things. You could use a special tools for this task, like xmorph (http://xmorph.sourceforge.net/). But to do the tween between two bitmap images you STILL need to set points. It's not tracing, but very similar. Anyway, result may be poor and I'd better suggest to use technique, described in Walking Cycle Tutorial or which the [[User:Pxegeek|Pxegeek]] meant. --[[User:Zelgadis|Zelgadis]] 02:08, 25 November 2007 (EST)

:::: There is a technique called "optical flow". It takes two input frames and calculates the movement of each individual pixel between the frames, allowing interpolation to be done. Here's an example: http://www.fxguide.com/article333.html. It doesn't require setting of control points, but it has problems it's own set of problems: http://www.fxguide.com/article333.html. --[[User:Yoyobuae|Yoyobuae]] 13:32, 3 February 2008 (EST)

=== Auto-link option in [[Draw tool]] ===

(4) so that you can draw a line, and have its endpoint automatically link to a duck - or if Auto-connect is off, you can get a line object linked to the end of another line object. / I missed this too, it even should be like that by default I think. [[User:Maxy|Maxy]] 13:22, 25 Apr 2006 (PDT)

: Isn't this done already? We don't have line objects, but blines are automatically linked to if auto-connect is on. Am I missing something? -- [[User:Dooglus|dooglus]] 17:29, 27 September 2007 (EDT)

::To clarify dooglus' comments - If you have an outline created by the draw tool highlighted in the layer dialog and the auto-extend checkbox is checked, then you can continue drawing with the draw tool in that same layer. Blines created with the Bline tool cannot be extended once a different tool or layer is selected. [[User:Pxegeek|Pxegeek]] 23:46, 12 October 2007 (EDT)

::: A line is a line - Synfig doesn't remember whether it was created with the Bline tool or the Draw tool - so you can extend blines created with the bline tool using the draw tool. Just make sure the line is selected (so that its ducks are visible), not looped (so that it has end points to extend from), enable the draw tool, check 'auto extend' and start drawing at one of its end ducks. [[User:Dooglus|dooglus]] 05:47, 13 October 2007 (EDT)

So this sounds like it is already done. But on a related note, being able to open an existing bline in the bline tool to extend it would be useful. -- [[User:Dooglus|dooglus]] 04:51, 29 January 2008 (EST)

=== Layer hide boolean parameter ===

(3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Panel]], and builds upon it as well, allowing the [[Layers Panel]] to dynamically unclutter. ''(This feature request is a refactoring of the [[Amount Parameter]])''
: With the addition of the [[Convert#Switch|Switch]] type conversion it is not needed this feature request. You can convert the Amount parameter to a Switch value and give 0 and 1 to the Linked OFF/ON values. --[[User:Genete|Genete]] 13:20, 29 October 2007 (EDT)

=== Riding ducks ===

(2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.
:Already done in SVN.[[User:Genete|Genete]] 18:59, 5 April 2008 (EDT)

=== Image filmstrip import ===

(2) — Allow import of a series of images (TGA, etc) as frames of an animation, on a layer. 
Response - 'lst' files of a list of images can be imported. I've used this to develop a walk cycle. See [[Walk_Cycle|Walk cycle]] for an example. [[user:pxegeek|pxegeek]]

=== Character Animation Tools ===

I have seen some interesting methods for helping character design/animation in different 2d/3d software. Hash's animation master has 'poses' which are extremes of a model, for example smiling and frowning, once you add these extremes ot a set you can use slider to create a pose that somewhere inbetween. The real power of this is when you have serveral different poses on the same object, a face say, you can easily come up with new facial expressions. Maybe something similar could be done with synfig using layers and groups, the implementation could something similar to Moho's switch layers. --[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)
: Have you read this tutorial? [[Reuse Animations]]. It is very close to the Switch layer of Moho/Anime Studio. Also You can change the Canvas parameter to any other canvas dynamically in the time line by clicking on it and selecting other exported canvas. Other option is convert the canvas to a Switch type and alternate between two different canvas. --[[User:Genete|Genete]] 13:26, 29 October 2007 (EDT)

=== More Animation Tools ===

[[New Animation Tools|Added here]]

=== Improved User Experience for First Contact ===
* Single file download and installer (at least for Windows)
* Ability to draw the first object directly after starting the application (start with an empty document)
* Ability to animate the object directly after drawing the first object (new documents have a say 3 seconds timeline)
In my opinion this is crucial to attract potential users. Because if I see how easy it is to create my first animation I'm going to accept all the bugs and clumsyness. A good example is the Pencil animation software. --[[User:Dmd|Dmd]] 13:50, 26 January 2008 (EST)

: I've implemented #2 and #3 above in svn r1519 & 1520. If no files are specified to be opened when running studio, it'll make a new one. It won't pop up the canvas properties dialog when making new canvases by default. And the default end time is 5s (3s is small enough to cause the time slider to show "1s 12f", whereas 5s looks cleaner). -- [[User:Dooglus|dooglus]] 04:00, 29 January 2008 (EST)

=== Automatic attach and manipulate a Vertex to a Bline ===

Please see [[Inverse Duck Manipulation|this]] page to understand what we want. --[[User:Genete|Genete]] 12:43, 3 March 2008 (EST).
:Already done in SVN. [[User:Genete|Genete]] 19:00, 5 April 2008 (EDT)

=== Toggle visible ducks ===
(3) So pressing, say, tab while editing a Bline toggles which vertices/ducks are visible - so we can easily move the actual vertices around without having the view cluttered by tangeants (and also make it easier to select 'Loop' rather than 'Split Tangeants' when creating the thing.)

Given that extra ducks such as the width ones listed above may be added, this might become more and more necessary. If too many different sets are added for toggling to be feasible, each visibility for each set can be hotkeyed.

: Synfig already have hotkeys to toggle visibility of the ducks. See [[Keyboard_Shortcuts#Hotkeys_Visual_Guide]]. --[[User:Zelgadis|Zelgadis]] 00:39, 22 April 2008 (EDT)

Doc:How Do I

2009-01-07T22:07:36Z

Creek23: /* How to change shortcut keys? */ fixed format

[[Category:Tutorials]]

Feel free to add your own questions here or [[Contact|contact]] us with them. Or put them on the [[Wiki Wish List]].

__TOC__

== Insert some text? ==

With recent development versions, there is a text tool. If you are using 0.61.08 or earlier, use right click on your canvas and choose Layer > New > Other > Text.

== How to change shortcut keys? ==
'''1.''' Find your Synfig config file under:
''Ubuntu GNU/Linux:'' /home/{username}/Synfig/
''Windows XP:'' C:\Documents and Settings\{username}\Synfig\
''Windows Vista:'' C:\Users\{username}\Synfig\
'''2.''' Open the file, named '''accelrc''', using any text editing software (GEdit, Kate, Notepad).

'''3.''' Change the shorcuts you want, save and close.

== How to have a Flash-like shortcut keys? ==
'''1.''' Follow the step on [[Tips#How_to_change_shortcut_keys.3F|how to change shortcut keys]], except for step 3.

'''2.''' Copy the code below and paste it on the very last part of '''accelrc''' then save and close it.
<code>
; misc
(gtk_accel_path "<Actions>//redo" "<Control>y")
; tools
(gtk_accel_path "<Actions>//state-text" "t")
(gtk_accel_path "<Actions>//state-rectangle" "r")
(gtk_accel_path "<Actions>//state-rotate" "<Shift>q")
(gtk_accel_path "<Actions>//state-zoom" "z")
(gtk_accel_path "<Actions>//state-polygon" "n")
(gtk_accel_path "<Actions>//state-bline" "p")
(gtk_accel_path "<Actions>//state-normal" "v")
(gtk_accel_path "<Actions>//state-eyedrop" "i")
(gtk_accel_path "<Actions>//state-fill" "k")
(gtk_accel_path "<Actions>//state-circle" "o")
(gtk_accel_path "<Actions>//state-scale" "q")
(gtk_accel_path "<Actions>//state-gradient" "g")
; navigation
(gtk_accel_path "<Actions>//seek-next-frame" "period")
(gtk_accel_path "<Actions>//seek-prev-frame" "comma")
</code>

== Apply a gradient to an object instead of the entire canvas? ==

# Create the region you want to fill with a gradient, and the gradient layer, if you haven't already.
# Make sure that the gradient layer is above the region layer in the [[Layers Panel]].
# Select both layers, right click, and select [[Encapsulate]].
# Expand the new [[Paste Canvas|Inline Canvas]] layer if it's not already, and select your gradient layer.
# In the [[Params Panel]] select the [[Blend Method]] parameter, and choose [[Blend Method#Onto|Onto]] from the drop-down menu.

The gradient will clip to the visible area of the region below it inside the [[Paste Canvas|Inline Canvas]]. (and any other layers in that section).

== Show or hide a layer, or fade the effect of a blur? ==
In the [[Params Panel]], look for an option labeled [[Amount Parameter|Amount]] - this controls how much of the blended result of the layer is composited with the blend of the layers beneath it.

In other words, for a typical layer, this will 'fade it out'. For a [[Blur Layer]] set to "[[Blend Method#Straight|Straight]]", this will fade ''between'' the blurred version and the unblurred version of the canvas. If you want it to become less blurry, adjust the [[Blur Layer#Size|Blur Layer's 'size' parameter]].

== Fill an outline? ==
(Requested by [[User:Karlb|Karlb]])

There are several options:
* The easiest way is to link a new region layer to the outline's shape.
*# Select the outline you want to fill.
*# In the Params Panel, right-click the Vertices parameter, select "Export", enter a name for the shape, and hit return. This will export the shape of the outline, making it visible in the Children dialog.
*# In the Children dialog, open the ValueBase Nodes tree and select the name you just saved the shape as.
*# From the [[Layer Menu]] (either context-click on the [[Layers Panel]] or use the [[Canvas Menu Caret]]) create a new [[Region Layer]] by selecting "New Layer -> Geometry -> Region". Ensure that the created layer is selected.
*# In the parameter dialog, right-click the Vertices parameter and click "Connect".
*# Now, if you don't need exported shape, you can unexport it: right click name of the shape in the Children dialog and click "Unexport".
* Similar to the above, but using a different method:
*# Create a new region layer as above, and leave it selected.
*# Don't make any changes to the outline layer, which you want to fill! (see the Tier 5 on the [[Linking]] page for details).
*# Select both layers in the [[Layers Panel]] This will display only the parameters shared by both layers in the [[Params Panel]].
*# Context-click on the [[Vertices Parameter]], and select [[Linking|Link]].
*# The [[Region Layer]] will snap to the shape of the [[Outline Layer]].
* When you create an [[Outline Layer|outline]] with the [[Bline Tool]] that you intend to be a filled area as well, make sure you select the Fill checkbox in the [[Bline Tool#Options|tool options dialog]]. Obviously, this doesn't help much if you realise later that you needed a fill here.
* If you are using the [[draw tool]], there is a button at the bottom of the [[draw tool#Options|tool options dialog]] labeled "Fill Last Stroke", which creates a new [[Region Layer]] and links its shape to the previously drawn outline. Unfortunately, it doesn't work as of Synfig Studio v0.61.04. It has been fixed in the current SVN version of the code.
* Create a [[Region Layer|region]] with the same number of ducks, and manually link each duck. If you want a region that depends on multiple outline layers, this is really your only choice for now.
* Use the draw tool, select only the outline to fill, draw a stroke roughly following the outline and make sure you're holding the Control key when you left go of the mouse button at the end of the stroke. This doesn't work 100% right at the moment.

== Dock windows together? ==

*To dock (join) separate windows into one you must drag the tab ''icons'' for each of the tools into another window.
*You can create subdivisions inside the windows by dragging the icons into the side tabs (located around the edges, the look like rectangles).
*Tool tabs inside the window can be arranged by dragging them on top of one another, therefore changing the order.
*''How Do I min/maximize all Synfig windows on a Windows pc''? There must be an easy way/tool to do this?

== Use an external bitmap? ==

* In the image menu (>) choose file-->import. PNG with alpha channel works fine.
* To animate it without accidental stretching, right-click on the layer and choose encapsulate. You can then animate the position of the new "Inline Canvas" layer instead of the bbox.

== Use an image as a fill colour? ==

Make a new object (bline, region, squares, circles, polygons all work)
Import the image you want as the fill colour, and put it on the layer underneith your object. Set the blend method of the image (using the [[Parameters Palette]]) to "onto" or "straightonto".
Encapsulate the object and the fill colour image, otherwise everthing below the image will have the same fill colour.
Be sure to have a look at what the other composite options do as well.

== Use an external Vector? ==

Synfig doesn't yet support vector import because no-one has written an import process yet. You can use the Svg2synfig [[Converters|converter]], or import it as a bitmap and trace over it in synfig. If you want to implement vector import we would gladly accept your patch.

== Close a bline? ==

* Right click on the starting point and then click on loop bline.

Note: It doesn't work unless the initial point has a tangent - ie the first segment is curved. But you can hide tangent ducks (Alt+3, or "Caret Menu > View > Show/Hide Ducks > Show tangent ducks") and process as described. Don't forget to press (Alt+3) after that to show tangent ducks again.

== How do I transform encapsulated objects? ==

* Right click on the Encapsulated object in the Layer dialog and choose "select all child layers". Then you select the ducks you want to transform (usually just all of them, like for rotating the object), and the rotate or scale tool and do the work.

== Make objects go behind each other, without moving layers? ==

You'll notice each layer you make has a number in the z depth column in the Layers Panel. Say you have 3 layers, they will be numbered 2 (lowest, e.g. a square) 1 (eg a circle) 0 (highest, the default, e.g. a line). In order to make layer 1, the circle, pass behind layer 2, the square, change its z depth to be 3 or more. The z depth of the circle needs to be greater than 2 in order to be behind the square. To make the square on top of everything, you'd change its z depth to -1 or less.

Positive numbers on the z axis go into the screen, and negative numbers go out of the screen, towards the viewer.

It is possible to animate this effect, but each layer is discrete. They seem to go from 0 to 0.9999.

In addition, objects in encapsulated layers can only go behind other objects in the same encapsulated layer. However an encapsulated layer can go behind another encapsulated layer.

== Copy a complex convert combination between parameters of different layers? ==

For example: you want to copy a complicated [[Convert|conversion]] type that you have in one parameter from a layer, to other parameter (maybe not a root parameter, but a sub-parameter) of other layer. If you [[Export|export]] the complicated conversion type from the original layer and then go to the other layer and select [[Connect]] (right click and the exported and the parameter both selected) then you have the parameter form the second layer to be exactly the same than the original one. But there is a drawback: if you modify one of the sub-parameters in the complicated conversion type (e.g. you change the value of one of them) then automatically the same sub-parameter of the other layer is changed.

How can you copy the conversion but allow modify the sub-parameters independently on each layer?

Once you have achieved the complex conversion type in the original layer, don't export the root parameter! If you have done yet [[Export|unexport]] it. (Why?. You will understand it later.) Now duplicate the original layer. Then you should obtain the same layer with the same conversion type placed at the same parameter (but not exported). NOW export the parameter from the duplicated layer. Then go to the (sub) parameter of the layer where you want to copy the complex conversion type and Connect it to the just exported parameter form the duplicated layer. Now delete the duplicated layer (!). Then the exported [[ValueNode]] still undeleted and the layer where you wanted to copy the complex convert type have a (sub) parameter connected to it. You can [[Export|unexport]] the ValueNode or not. It is up to you. But notice that the conversion type is already copied into other (sub) parameter of other layer and they are independent as well as you can change one of them (by modifying the sub-parameters) and the other remains untouched.

== Make an existing animation run at half speed? ==

If you have an animation that runs from 0s to 10s and you want it to run at half speed from 0s to 20s, how can you do that?

* Either: encapsulate it, and use the 'time offset' parameter in the encapsulation layer to slow it down:
** Right-click 'time offset' in the encapsulation layer, convert>linear, rate -0.5 offset 0. That means offset the time by -0.5 seconds per second - or in other words, run at half speed
** Or, putting waypoints on the 'time offset' param would work too: 0 at 0s and -10 at 20s. (The choice between using a linear convert and valuenodes is entirely up to you. They both achieve the same result in this simple case).

* Or: use a [[Time Loop Layer]]. The first method seems better and more intuitive in this case, but there are ways of getting the same effect from the Time Loop layer. Perhaps the Time Loop layer is better if the animation doesn't run from 0s, but from some other time. Anyway: put a Time Loop layer over the layers you wish to slow down, and:
** Either: set duration to 0, local time to 0, convert->linear the link time and set rate to 0.5 - this slows the animation down *to* 50% of its original speed; use bigger rates to slow it down less
** Or: set duration to 1h (*), link time to 0, convert->linear the local time and set rate to 0.5 - this slows the animation down *by* 50%; use bigger rates to slow it down more
(*) if your animation is longer than 1h then set this parameter to EOT (End Of Time) what is the same as Infinite (INF) for a real number but for a time parameter.

== Draw a rectangle with a given width and height? ==

I was asked on IRC how to specify the width and height of a rectangle, rather than having to specify the position of two opposite corners. Here's how:

* draw a rectangle
* go to the [[Params Panel]]
* right-click the 'point 1' parameter and [[Export]]
* give it a name, "p1" say
* right-click the 'point 2' parameter and [[Convert]] to [[Convert#Add|Add]]
* (that's saying that rather than specifying the absolute position of the other point, you want synfig to calculate it for you)
* (it will make 2 new sub-parameters for 'point 2', and the value used for point 2 will be their sum so we want to tell it to use 'point 1' and your (width,height))
* open up the sub-parameters of 'point 2' by clicking the triangle to its left
* go to the [[Children Panel]], open up the values and select the one you exported earlier (p1)
* right-click the "LHS" parameter in the parameters dialog and [[Connect]] it
* then enter the width and height you want in the 'RHS' parameter

== Make linked BLine vertices not affected by Rotate layer? ==
Look at the http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-02-07.log
See also: [[Convert]].

== Create dashed outlines? ==

If you want to make simple dashed outlines the faster way is proceed like this:

* Create a Curve Gradient and an Outline over the same [[Bline]] using the [[Bline Tool]] options. Check both Outline and Gradient at the [[Tool Options Panel]].
* Raise up the gradient layer (it is created below the [[Outline Layer]]).
* Modify the gradient [[Blend Method]] parameter to be Straight Onto. That would render the gradient onto the outline width. Also it wouldn't render the outline, so transparent portions of the gradient are transparent.
* Check the 'Perpendicular' parameter of the Curve Gradient Layer.
* [[Convert]] the Gradient Parameter of the Curve Gradient Layer to be one of those types: Stripes or Repeat Gradient.
* Modify the properties of the sub parameters to achieve the desired effect.

== Render to AVI with higher quality? ==

=== Using raw video ===
The module used by Synfig to render AVI files is ffmpeg. For the moment there is not interface to control ffmpeg options so you render with a fixed bitrate and quality. If you want the maximum quality in your AVI file, follow these steps:

* Render your animation to yuv420p format. To do that select that target at the drop down list of the render dialog and add the ".yuv" extension to your animation name (without quotes).
* Once rendered (it would produce a huge size yuv file) you can quickly convert it to AVI using this command:

ffmpeg -i animation.yuv -sameq animation.avi

Change the animation file name to your one.

=== Rendering trough png sequence. ===
Render your sif to png sequence
mkdir render
synfig my_animation.sifz -o render/frame.png
Then convert it to movie with ffmpeg
ffmpeg -r <frame rate> -i render/frame.%04d.png <more settings from ffmpeg's manual> my_animation.mov
If you need nice open source format without any tweaks you may try ffmpeg2theora:
ffmpeg2theora render/frame.%04d.png --inputfps <frame rate> -o my_animation.ogg
png takes less disk space then yuv.
--[[User:AkhIL|AkhIL]] 21:38, 9 April 2008 (EDT)

==Increase performance by optimizing during compilation time? ==

I would like to know what parameters do I need to apply to configure to improve performance. [[User:Genete|Genete]] 11:04, 9 April 2008 (EDT)

To optimize program you should set two environment variables
export CFLAGS=""
export CXXFLAGS=$CFLAGS

First flag will be "-O3" (ow three). "-02" is normal optimization. "-03" is hard optimisation.

Now you should get info about your CPU
cat /proc/cpuinfo

find your cpu model name

now go to man gcc and searc "-mtune"

find your cpu and add "-mtune=your-cpu -march=your-cpu" to CFLAGS.

Then look at flags from /proc/cpuinfo and search it in gcc manual
For example I have 3dnow. So I can find "-m3dnow". For sse I can find "-msse" and "-mfpmath=sse" (can make program unstable).

Finaly you may add "-ffast-math" to disable math checks. But it can make program unstable.

For my AthlonXP I'm using this flags:
export CFLAGS="-O3 -pipe -mtune=athlon-xp -march=athlon-xp -mmmx -msse -m3dnow -mfpmath=sse -ffast-math -funsigned-char -fno-strict-aliasing"
export CXXFLAGS=$CFLAGS
--[[User:AkhIL|AkhIL]] 12:05, 9 April 2008 (EDT)

For my Pentium3 i use the line:
export CFLAGS="-O3 -pipe -mtune=pentium3 -march=pentium3 -msse -mfpmath=sse -funsigned-char -fno-strict-aliasing"
export CXXFLAGS=$CFLAGS

The additional switches -mmmx and -ffast-math does seem to '''not''' yield any gain in computing performance! So you could leave them out.
--[[User:SvH|SvH]] 03:46, 20 May 2008 (EDT)

== Import a movie into Synfig? ==

To import a movie (image only, not sound) into synfig there is only one option for the moment: Extract an image sequence from the movie and import them using [[ListImporter]]. Before you can load the image sequence you have to extract it from the movie. There are several software to do that but a straight and easy way is to use mplayer:

mplayer mymovie.avi -vo png:z=1 -ss seconds-start -endpos duration

where ''seconds-start'' are the seconds where you want to extract form and ''duration'' is the number of seconds you want to extract from ''mymovie.avi''. Also the image format specified in this case is png but jpeg or tga can be used also. See [http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html mplayer manual page] for more info.

It would extract a set of files of the selected section of the movie. Each file takes the frame number padded with leading zeros as name.

To put all the filenames into a ''.lst'' file just type this in the folder wehre the files are:

ls *.png >> mymovie.lst

and add a line specifying the frame rate at the beginning of the text file:

FPS 25

if the movie was 25 fps.

== Granted Wishes ==

=== MNG target filetype ===

The ability to save as/in the Free/Open MNG (.mng) format [http://libpng.org/pub/mng/]

A partial implementation was committed in SVN r470.

It was implemented in svn 986. See [[Render options]]. --[[User:Genete|Genete]] 13:12, 29 October 2007 (EDT)

=== Optionally display RGB in Hex in Color dialog ===

(3) When colors are quoted as 3 bytes of hexadecimal, you have to convert them to decimal, divide by 255, multiply by 100 to get a number to type into the dialog box. It's painful to match color schemes for example, with the [http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines Tango Icon Theme style guidelines]. [[User:pxegeek|PXEGeek]] 3/16/07

: Added in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=40dda9d27b5249ee32f62d84c819ff569f078929 svn r354]. You can type 3 or 6 digit hex codes and hit return to use. 3 digit code 36a gives colour 3366aa (each digit is duplicated) -- [[User:Dooglus|dooglus]] 3/18/07

:: Many thanks - already used many times! PXEGeek.

::: Did you notice that you can use single digit codes too? '5' gives 555555 for instance, giving you 16 equally spaces shades of black through white. -- [[User:Dooglus|dooglus]] 17:51, 25 September 2007 (EDT)

=== Restore Default Layout ===

(3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.
-> I'd like to second this one - especially with the bug where dialog boxes sometime shrink to nothing or offscreen, and no amount of maximizing or minimizing restores them. The only solution is to kill the windows, and none of the combo options in the dialog menu match the default configuration. 4/4/07 PXEGeek

: Implemented in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=036306f3c2c265a604971728d50fcce258766552 svn r757] -- [[User:Dooglus|dooglus]] 17:48, 25 September 2007 (EDT)

=== General outline / Polygon-based Outline / "Set Tangents to Zero" button ===
(3.5) I'm no artist, thus my primary form of art is stick figures, not to mention, many interesting animations are done in stick-figure style. Stick figures must be perfectly straight to get the effect across, so when I'm making an outline using B-Curves, it is too time consuming to set the tangents to 0 each time. Similarly, outlines of other shapes like squares, circles and so forth would be very useful. Whichever of the above is easiest, please implement right away. --[[User:Dragontamer|Dragontamer]] 02:35, 19 November 2007 (EST)
: For perfectly straight lines, click without moving the mouse. You will get a single point with no tangents. Outline shapes would require some development, particularly with some thought given to backward compatibility. A workaround you might consider is to create a duplicate shape with a different color and make the top one slightly smaller, so the outline of the one below shows. [[User:Pxegeek|Pxegeek]] 21:58, 19 November 2007 (EST)
:: Well, in general, whenever I click on a point to edit it (say, to make it move somewhere in animation mode), there is a decent chance that I click on a tangent instead. Then, if I want to right click the point itself, I usually right click the tangent marker instead. It isn't that big a deal, but simplicity at the cost of power generally is a good thing, especially when it will save a few mouse clicks.
:: As for the outlines, yeah, I've tried that and it is a decent solution for now, although it is no replacement for a real outline. I am going to also experiment with a clamp to see if I can make the center of the shape have 100% alpha... but I don't have synfig on the computer I'm on right now. Thanks for the tips Pxegeek. --[[User:Dragontamer|Dragontamer]] 01:58, 27 November 2007 (EST)
::: You can press Alt+3 to hide tangent ducks. --[[User:Zelgadis|Zelgadis]] 09:27, 27 November 2007 (EST)

=== Copy & Paste/Image Importing ===

(4) I sometimes make graphics in other programs, or use clipart and other images. Would it be possible for Synfig to be able to import images and/or copy and paste them?--Khlieeq 2007-07-19
Well, it doesn't support Copy & paste from the clipboard, but you can import images using "New Layer -> Other -> Import". This will create an Import layer, for which you can then edit the properties to point to the file containing your image. PXEGeek. 2007-07-19

=== Recursive Waypoint Manipulation ===

(4) it is really tiresome to revert changes to waypoints created by manipulating tangent/position ducks or change their interpolation functions. making it possible to right-click-modify the waypoint shown for objects that have some waypoint in a referenced sub-object would be great! -- timonator 2007-06-01
:You can do it in two ways: changing the interpolation method of the waypoint of paste canvas or editing the keyframe properties. The first allow to modify the waypoints interpolation method for all the waypoints of all the parameters of all the layers that are inside the paste canvas layer. You can right click on the left or right part of the waypoint to edit by a context menu the left or the right interpolation method of the waipoints. The second method would add and modify all the parameters that have any waypoint in the animation. See [[Keyframe]] for more detail. --[[User:Genete|Genete]] 13:10, 29 October 2007 (EDT)

=== Tweening for images developed in other imaging programs ===

It's obvious I am a beginner at image movement, but morphing is not enough: movement across the page is needed. Thanks for listening. [[User:Comwell@bellsouth.net|Comwell]] 
Imported images can be moved across the page. They can also be scaled, rotated and deformed. Was there a specific example you had in mind? [[User:Pxegeek|pxegeek]] 
:I also would like a way to tween images that have been drawn in other programs. I've had trouble drawing with Bline tool and the drawing tool in Synfig, and I'd rather just draw with a paint brush (like the one in Photoshop). Another problem I have is that Synfig tends to shut down on me every 20 minutes or so, and it's really frustrating even with the auto recover feature, because my sketches disappear. It'd be nice if I'm able to draw all of the keyframes in Photoshop or another image program and import it to Synfig so that Synfig can tween and animate them. Thank you. [[User:xychefoo@gmail.com|Huina]]
::You CAN use images, drawn in other programs. Just select "File->Import" from [[Canvas Menu Caret|canvas menu]] --[[User:Zelgadis|Zelgadis]] 01:39, 24 November 2007 (EST)
:::But how do you animate using images from other sources? I tried to make 2 keyframes with 2 different images, and it doesn't animate. It just stays as 1 picture for the entire render. The closest thing I saw to importing images from another source into Synfig and having it animate is the Walking Cycle Tutorial, but I would still have to trace the images to make it animate. As I said earlier, I'm not entirely fond of using the draw/Bline tool. [[User:xychefoo@gmail.com|Huina]]
:::: Huina, there's no way to do what you want right now. Interpolating between two images that are not created in Synfig is well beyond its scope right now. However, what you could do is take an image and separate elements of the picture onto different layers (e.g. have a picture of an arm and another of the rest of the body) and you can move those around, stretch and rotate them. (If you're familiar with the work of Terry Gilliam on Monty Python you'll know what I mean) I don't know how feasible it is to implement your request (I suspect some heavy lifting). We'll keep it on the list, but don't hold your breath. [[User:Pxegeek|Pxegeek]] 19:57, 24 November 2007 (EST)

:::: I think, you hardly find any other animation package which allow you to do such things. You could use a special tools for this task, like xmorph (http://xmorph.sourceforge.net/). But to do the tween between two bitmap images you STILL need to set points. It's not tracing, but very similar. Anyway, result may be poor and I'd better suggest to use technique, described in Walking Cycle Tutorial or which the [[User:Pxegeek|Pxegeek]] meant. --[[User:Zelgadis|Zelgadis]] 02:08, 25 November 2007 (EST)

:::: There is a technique called "optical flow". It takes two input frames and calculates the movement of each individual pixel between the frames, allowing interpolation to be done. Here's an example: http://www.fxguide.com/article333.html. It doesn't require setting of control points, but it has problems it's own set of problems: http://www.fxguide.com/article333.html. --[[User:Yoyobuae|Yoyobuae]] 13:32, 3 February 2008 (EST)

=== Auto-link option in [[Draw tool]] ===

(4) so that you can draw a line, and have its endpoint automatically link to a duck - or if Auto-connect is off, you can get a line object linked to the end of another line object. / I missed this too, it even should be like that by default I think. [[User:Maxy|Maxy]] 13:22, 25 Apr 2006 (PDT)

: Isn't this done already? We don't have line objects, but blines are automatically linked to if auto-connect is on. Am I missing something? -- [[User:Dooglus|dooglus]] 17:29, 27 September 2007 (EDT)

::To clarify dooglus' comments - If you have an outline created by the draw tool highlighted in the layer dialog and the auto-extend checkbox is checked, then you can continue drawing with the draw tool in that same layer. Blines created with the Bline tool cannot be extended once a different tool or layer is selected. [[User:Pxegeek|Pxegeek]] 23:46, 12 October 2007 (EDT)

::: A line is a line - Synfig doesn't remember whether it was created with the Bline tool or the Draw tool - so you can extend blines created with the bline tool using the draw tool. Just make sure the line is selected (so that its ducks are visible), not looped (so that it has end points to extend from), enable the draw tool, check 'auto extend' and start drawing at one of its end ducks. [[User:Dooglus|dooglus]] 05:47, 13 October 2007 (EDT)

So this sounds like it is already done. But on a related note, being able to open an existing bline in the bline tool to extend it would be useful. -- [[User:Dooglus|dooglus]] 04:51, 29 January 2008 (EST)

=== Layer hide boolean parameter ===

(3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Panel]], and builds upon it as well, allowing the [[Layers Panel]] to dynamically unclutter. ''(This feature request is a refactoring of the [[Amount Parameter]])''
: With the addition of the [[Convert#Switch|Switch]] type conversion it is not needed this feature request. You can convert the Amount parameter to a Switch value and give 0 and 1 to the Linked OFF/ON values. --[[User:Genete|Genete]] 13:20, 29 October 2007 (EDT)

=== Riding ducks ===

(2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.
:Already done in SVN.[[User:Genete|Genete]] 18:59, 5 April 2008 (EDT)

=== Image filmstrip import ===

(2) — Allow import of a series of images (TGA, etc) as frames of an animation, on a layer. 
Response - 'lst' files of a list of images can be imported. I've used this to develop a walk cycle. See [[Walk_Cycle|Walk cycle]] for an example. [[user:pxegeek|pxegeek]]

=== Character Animation Tools ===

I have seen some interesting methods for helping character design/animation in different 2d/3d software. Hash's animation master has 'poses' which are extremes of a model, for example smiling and frowning, once you add these extremes ot a set you can use slider to create a pose that somewhere inbetween. The real power of this is when you have serveral different poses on the same object, a face say, you can easily come up with new facial expressions. Maybe something similar could be done with synfig using layers and groups, the implementation could something similar to Moho's switch layers. --[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)
: Have you read this tutorial? [[Reuse Animations]]. It is very close to the Switch layer of Moho/Anime Studio. Also You can change the Canvas parameter to any other canvas dynamically in the time line by clicking on it and selecting other exported canvas. Other option is convert the canvas to a Switch type and alternate between two different canvas. --[[User:Genete|Genete]] 13:26, 29 October 2007 (EDT)

=== More Animation Tools ===

[[New Animation Tools|Added here]]

=== Improved User Experience for First Contact ===
* Single file download and installer (at least for Windows)
* Ability to draw the first object directly after starting the application (start with an empty document)
* Ability to animate the object directly after drawing the first object (new documents have a say 3 seconds timeline)
In my opinion this is crucial to attract potential users. Because if I see how easy it is to create my first animation I'm going to accept all the bugs and clumsyness. A good example is the Pencil animation software. --[[User:Dmd|Dmd]] 13:50, 26 January 2008 (EST)

: I've implemented #2 and #3 above in svn r1519 & 1520. If no files are specified to be opened when running studio, it'll make a new one. It won't pop up the canvas properties dialog when making new canvases by default. And the default end time is 5s (3s is small enough to cause the time slider to show "1s 12f", whereas 5s looks cleaner). -- [[User:Dooglus|dooglus]] 04:00, 29 January 2008 (EST)

=== Automatic attach and manipulate a Vertex to a Bline ===

Please see [[Inverse Duck Manipulation|this]] page to understand what we want. --[[User:Genete|Genete]] 12:43, 3 March 2008 (EST).
:Already done in SVN. [[User:Genete|Genete]] 19:00, 5 April 2008 (EDT)

=== Toggle visible ducks ===
(3) So pressing, say, tab while editing a Bline toggles which vertices/ducks are visible - so we can easily move the actual vertices around without having the view cluttered by tangeants (and also make it easier to select 'Loop' rather than 'Split Tangeants' when creating the thing.)

Given that extra ducks such as the width ones listed above may be added, this might become more and more necessary. If too many different sets are added for toggling to be feasible, each visibility for each set can be hotkeyed.

: Synfig already have hotkeys to toggle visibility of the ducks. See [[Keyboard_Shortcuts#Hotkeys_Visual_Guide]]. --[[User:Zelgadis|Zelgadis]] 00:39, 22 April 2008 (EDT)

Doc:How Do I

2009-01-07T22:06:50Z

Creek23: /* How to have a Flash-like shorcut keys */ added link

[[Category:Tutorials]]

Feel free to add your own questions here or [[Contact|contact]] us with them. Or put them on the [[Wiki Wish List]].

__TOC__

== Insert some text? ==

With recent development versions, there is a text tool. If you are using 0.61.08 or earlier, use right click on your canvas and choose Layer > New > Other > Text.

== How to change shortcut keys? ==
'''1.''' Find your Synfig config file under:
''Ubuntu GNU/Linux:'' /home/{username}/Synfig/
''Windows XP:'' C:\Documents and Settings\{username}\Synfig\
''Windows Vista:'' C:\Users\{username}\Synfig\
'''2.''' Open the file, named '''accelrc''', using any text editing software (GEdit, Kate, Notepad).
'''3.''' Change the shorcuts you want, save and close.

== How to have a Flash-like shortcut keys? ==
'''1.''' Follow the step on [[Tips#How_to_change_shortcut_keys.3F|how to change shortcut keys]], except for step 3.

'''2.''' Copy the code below and paste it on the very last part of '''accelrc''' then save and close it.
<code>
; misc
(gtk_accel_path "<Actions>//redo" "<Control>y")
; tools
(gtk_accel_path "<Actions>//state-text" "t")
(gtk_accel_path "<Actions>//state-rectangle" "r")
(gtk_accel_path "<Actions>//state-rotate" "<Shift>q")
(gtk_accel_path "<Actions>//state-zoom" "z")
(gtk_accel_path "<Actions>//state-polygon" "n")
(gtk_accel_path "<Actions>//state-bline" "p")
(gtk_accel_path "<Actions>//state-normal" "v")
(gtk_accel_path "<Actions>//state-eyedrop" "i")
(gtk_accel_path "<Actions>//state-fill" "k")
(gtk_accel_path "<Actions>//state-circle" "o")
(gtk_accel_path "<Actions>//state-scale" "q")
(gtk_accel_path "<Actions>//state-gradient" "g")
; navigation
(gtk_accel_path "<Actions>//seek-next-frame" "period")
(gtk_accel_path "<Actions>//seek-prev-frame" "comma")
</code>

== Apply a gradient to an object instead of the entire canvas? ==

# Create the region you want to fill with a gradient, and the gradient layer, if you haven't already.
# Make sure that the gradient layer is above the region layer in the [[Layers Panel]].
# Select both layers, right click, and select [[Encapsulate]].
# Expand the new [[Paste Canvas|Inline Canvas]] layer if it's not already, and select your gradient layer.
# In the [[Params Panel]] select the [[Blend Method]] parameter, and choose [[Blend Method#Onto|Onto]] from the drop-down menu.

The gradient will clip to the visible area of the region below it inside the [[Paste Canvas|Inline Canvas]]. (and any other layers in that section).

== Show or hide a layer, or fade the effect of a blur? ==
In the [[Params Panel]], look for an option labeled [[Amount Parameter|Amount]] - this controls how much of the blended result of the layer is composited with the blend of the layers beneath it.

In other words, for a typical layer, this will 'fade it out'. For a [[Blur Layer]] set to "[[Blend Method#Straight|Straight]]", this will fade ''between'' the blurred version and the unblurred version of the canvas. If you want it to become less blurry, adjust the [[Blur Layer#Size|Blur Layer's 'size' parameter]].

== Fill an outline? ==
(Requested by [[User:Karlb|Karlb]])

There are several options:
* The easiest way is to link a new region layer to the outline's shape.
*# Select the outline you want to fill.
*# In the Params Panel, right-click the Vertices parameter, select "Export", enter a name for the shape, and hit return. This will export the shape of the outline, making it visible in the Children dialog.
*# In the Children dialog, open the ValueBase Nodes tree and select the name you just saved the shape as.
*# From the [[Layer Menu]] (either context-click on the [[Layers Panel]] or use the [[Canvas Menu Caret]]) create a new [[Region Layer]] by selecting "New Layer -> Geometry -> Region". Ensure that the created layer is selected.
*# In the parameter dialog, right-click the Vertices parameter and click "Connect".
*# Now, if you don't need exported shape, you can unexport it: right click name of the shape in the Children dialog and click "Unexport".
* Similar to the above, but using a different method:
*# Create a new region layer as above, and leave it selected.
*# Don't make any changes to the outline layer, which you want to fill! (see the Tier 5 on the [[Linking]] page for details).
*# Select both layers in the [[Layers Panel]] This will display only the parameters shared by both layers in the [[Params Panel]].
*# Context-click on the [[Vertices Parameter]], and select [[Linking|Link]].
*# The [[Region Layer]] will snap to the shape of the [[Outline Layer]].
* When you create an [[Outline Layer|outline]] with the [[Bline Tool]] that you intend to be a filled area as well, make sure you select the Fill checkbox in the [[Bline Tool#Options|tool options dialog]]. Obviously, this doesn't help much if you realise later that you needed a fill here.
* If you are using the [[draw tool]], there is a button at the bottom of the [[draw tool#Options|tool options dialog]] labeled "Fill Last Stroke", which creates a new [[Region Layer]] and links its shape to the previously drawn outline. Unfortunately, it doesn't work as of Synfig Studio v0.61.04. It has been fixed in the current SVN version of the code.
* Create a [[Region Layer|region]] with the same number of ducks, and manually link each duck. If you want a region that depends on multiple outline layers, this is really your only choice for now.
* Use the draw tool, select only the outline to fill, draw a stroke roughly following the outline and make sure you're holding the Control key when you left go of the mouse button at the end of the stroke. This doesn't work 100% right at the moment.

== Dock windows together? ==

*To dock (join) separate windows into one you must drag the tab ''icons'' for each of the tools into another window.
*You can create subdivisions inside the windows by dragging the icons into the side tabs (located around the edges, the look like rectangles).
*Tool tabs inside the window can be arranged by dragging them on top of one another, therefore changing the order.
*''How Do I min/maximize all Synfig windows on a Windows pc''? There must be an easy way/tool to do this?

== Use an external bitmap? ==

* In the image menu (>) choose file-->import. PNG with alpha channel works fine.
* To animate it without accidental stretching, right-click on the layer and choose encapsulate. You can then animate the position of the new "Inline Canvas" layer instead of the bbox.

== Use an image as a fill colour? ==

Make a new object (bline, region, squares, circles, polygons all work)
Import the image you want as the fill colour, and put it on the layer underneith your object. Set the blend method of the image (using the [[Parameters Palette]]) to "onto" or "straightonto".
Encapsulate the object and the fill colour image, otherwise everthing below the image will have the same fill colour.
Be sure to have a look at what the other composite options do as well.

== Use an external Vector? ==

Synfig doesn't yet support vector import because no-one has written an import process yet. You can use the Svg2synfig [[Converters|converter]], or import it as a bitmap and trace over it in synfig. If you want to implement vector import we would gladly accept your patch.

== Close a bline? ==

* Right click on the starting point and then click on loop bline.

Note: It doesn't work unless the initial point has a tangent - ie the first segment is curved. But you can hide tangent ducks (Alt+3, or "Caret Menu > View > Show/Hide Ducks > Show tangent ducks") and process as described. Don't forget to press (Alt+3) after that to show tangent ducks again.

== How do I transform encapsulated objects? ==

* Right click on the Encapsulated object in the Layer dialog and choose "select all child layers". Then you select the ducks you want to transform (usually just all of them, like for rotating the object), and the rotate or scale tool and do the work.

== Make objects go behind each other, without moving layers? ==

You'll notice each layer you make has a number in the z depth column in the Layers Panel. Say you have 3 layers, they will be numbered 2 (lowest, e.g. a square) 1 (eg a circle) 0 (highest, the default, e.g. a line). In order to make layer 1, the circle, pass behind layer 2, the square, change its z depth to be 3 or more. The z depth of the circle needs to be greater than 2 in order to be behind the square. To make the square on top of everything, you'd change its z depth to -1 or less.

Positive numbers on the z axis go into the screen, and negative numbers go out of the screen, towards the viewer.

It is possible to animate this effect, but each layer is discrete. They seem to go from 0 to 0.9999.

In addition, objects in encapsulated layers can only go behind other objects in the same encapsulated layer. However an encapsulated layer can go behind another encapsulated layer.

== Copy a complex convert combination between parameters of different layers? ==

For example: you want to copy a complicated [[Convert|conversion]] type that you have in one parameter from a layer, to other parameter (maybe not a root parameter, but a sub-parameter) of other layer. If you [[Export|export]] the complicated conversion type from the original layer and then go to the other layer and select [[Connect]] (right click and the exported and the parameter both selected) then you have the parameter form the second layer to be exactly the same than the original one. But there is a drawback: if you modify one of the sub-parameters in the complicated conversion type (e.g. you change the value of one of them) then automatically the same sub-parameter of the other layer is changed.

How can you copy the conversion but allow modify the sub-parameters independently on each layer?

Once you have achieved the complex conversion type in the original layer, don't export the root parameter! If you have done yet [[Export|unexport]] it. (Why?. You will understand it later.) Now duplicate the original layer. Then you should obtain the same layer with the same conversion type placed at the same parameter (but not exported). NOW export the parameter from the duplicated layer. Then go to the (sub) parameter of the layer where you want to copy the complex conversion type and Connect it to the just exported parameter form the duplicated layer. Now delete the duplicated layer (!). Then the exported [[ValueNode]] still undeleted and the layer where you wanted to copy the complex convert type have a (sub) parameter connected to it. You can [[Export|unexport]] the ValueNode or not. It is up to you. But notice that the conversion type is already copied into other (sub) parameter of other layer and they are independent as well as you can change one of them (by modifying the sub-parameters) and the other remains untouched.

== Make an existing animation run at half speed? ==

If you have an animation that runs from 0s to 10s and you want it to run at half speed from 0s to 20s, how can you do that?

* Either: encapsulate it, and use the 'time offset' parameter in the encapsulation layer to slow it down:
** Right-click 'time offset' in the encapsulation layer, convert>linear, rate -0.5 offset 0. That means offset the time by -0.5 seconds per second - or in other words, run at half speed
** Or, putting waypoints on the 'time offset' param would work too: 0 at 0s and -10 at 20s. (The choice between using a linear convert and valuenodes is entirely up to you. They both achieve the same result in this simple case).

* Or: use a [[Time Loop Layer]]. The first method seems better and more intuitive in this case, but there are ways of getting the same effect from the Time Loop layer. Perhaps the Time Loop layer is better if the animation doesn't run from 0s, but from some other time. Anyway: put a Time Loop layer over the layers you wish to slow down, and:
** Either: set duration to 0, local time to 0, convert->linear the link time and set rate to 0.5 - this slows the animation down *to* 50% of its original speed; use bigger rates to slow it down less
** Or: set duration to 1h (*), link time to 0, convert->linear the local time and set rate to 0.5 - this slows the animation down *by* 50%; use bigger rates to slow it down more
(*) if your animation is longer than 1h then set this parameter to EOT (End Of Time) what is the same as Infinite (INF) for a real number but for a time parameter.

== Draw a rectangle with a given width and height? ==

I was asked on IRC how to specify the width and height of a rectangle, rather than having to specify the position of two opposite corners. Here's how:

* draw a rectangle
* go to the [[Params Panel]]
* right-click the 'point 1' parameter and [[Export]]
* give it a name, "p1" say
* right-click the 'point 2' parameter and [[Convert]] to [[Convert#Add|Add]]
* (that's saying that rather than specifying the absolute position of the other point, you want synfig to calculate it for you)
* (it will make 2 new sub-parameters for 'point 2', and the value used for point 2 will be their sum so we want to tell it to use 'point 1' and your (width,height))
* open up the sub-parameters of 'point 2' by clicking the triangle to its left
* go to the [[Children Panel]], open up the values and select the one you exported earlier (p1)
* right-click the "LHS" parameter in the parameters dialog and [[Connect]] it
* then enter the width and height you want in the 'RHS' parameter

== Make linked BLine vertices not affected by Rotate layer? ==
Look at the http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-02-07.log
See also: [[Convert]].

== Create dashed outlines? ==

If you want to make simple dashed outlines the faster way is proceed like this:

* Create a Curve Gradient and an Outline over the same [[Bline]] using the [[Bline Tool]] options. Check both Outline and Gradient at the [[Tool Options Panel]].
* Raise up the gradient layer (it is created below the [[Outline Layer]]).
* Modify the gradient [[Blend Method]] parameter to be Straight Onto. That would render the gradient onto the outline width. Also it wouldn't render the outline, so transparent portions of the gradient are transparent.
* Check the 'Perpendicular' parameter of the Curve Gradient Layer.
* [[Convert]] the Gradient Parameter of the Curve Gradient Layer to be one of those types: Stripes or Repeat Gradient.
* Modify the properties of the sub parameters to achieve the desired effect.

== Render to AVI with higher quality? ==

=== Using raw video ===
The module used by Synfig to render AVI files is ffmpeg. For the moment there is not interface to control ffmpeg options so you render with a fixed bitrate and quality. If you want the maximum quality in your AVI file, follow these steps:

* Render your animation to yuv420p format. To do that select that target at the drop down list of the render dialog and add the ".yuv" extension to your animation name (without quotes).
* Once rendered (it would produce a huge size yuv file) you can quickly convert it to AVI using this command:

ffmpeg -i animation.yuv -sameq animation.avi

Change the animation file name to your one.

=== Rendering trough png sequence. ===
Render your sif to png sequence
mkdir render
synfig my_animation.sifz -o render/frame.png
Then convert it to movie with ffmpeg
ffmpeg -r <frame rate> -i render/frame.%04d.png <more settings from ffmpeg's manual> my_animation.mov
If you need nice open source format without any tweaks you may try ffmpeg2theora:
ffmpeg2theora render/frame.%04d.png --inputfps <frame rate> -o my_animation.ogg
png takes less disk space then yuv.
--[[User:AkhIL|AkhIL]] 21:38, 9 April 2008 (EDT)

==Increase performance by optimizing during compilation time? ==

I would like to know what parameters do I need to apply to configure to improve performance. [[User:Genete|Genete]] 11:04, 9 April 2008 (EDT)

To optimize program you should set two environment variables
export CFLAGS=""
export CXXFLAGS=$CFLAGS

First flag will be "-O3" (ow three). "-02" is normal optimization. "-03" is hard optimisation.

Now you should get info about your CPU
cat /proc/cpuinfo

find your cpu model name

now go to man gcc and searc "-mtune"

find your cpu and add "-mtune=your-cpu -march=your-cpu" to CFLAGS.

Then look at flags from /proc/cpuinfo and search it in gcc manual
For example I have 3dnow. So I can find "-m3dnow". For sse I can find "-msse" and "-mfpmath=sse" (can make program unstable).

Finaly you may add "-ffast-math" to disable math checks. But it can make program unstable.

For my AthlonXP I'm using this flags:
export CFLAGS="-O3 -pipe -mtune=athlon-xp -march=athlon-xp -mmmx -msse -m3dnow -mfpmath=sse -ffast-math -funsigned-char -fno-strict-aliasing"
export CXXFLAGS=$CFLAGS
--[[User:AkhIL|AkhIL]] 12:05, 9 April 2008 (EDT)

For my Pentium3 i use the line:
export CFLAGS="-O3 -pipe -mtune=pentium3 -march=pentium3 -msse -mfpmath=sse -funsigned-char -fno-strict-aliasing"
export CXXFLAGS=$CFLAGS

The additional switches -mmmx and -ffast-math does seem to '''not''' yield any gain in computing performance! So you could leave them out.
--[[User:SvH|SvH]] 03:46, 20 May 2008 (EDT)

== Import a movie into Synfig? ==

To import a movie (image only, not sound) into synfig there is only one option for the moment: Extract an image sequence from the movie and import them using [[ListImporter]]. Before you can load the image sequence you have to extract it from the movie. There are several software to do that but a straight and easy way is to use mplayer:

mplayer mymovie.avi -vo png:z=1 -ss seconds-start -endpos duration

where ''seconds-start'' are the seconds where you want to extract form and ''duration'' is the number of seconds you want to extract from ''mymovie.avi''. Also the image format specified in this case is png but jpeg or tga can be used also. See [http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html mplayer manual page] for more info.

It would extract a set of files of the selected section of the movie. Each file takes the frame number padded with leading zeros as name.

To put all the filenames into a ''.lst'' file just type this in the folder wehre the files are:

ls *.png >> mymovie.lst

and add a line specifying the frame rate at the beginning of the text file:

FPS 25

if the movie was 25 fps.

== Granted Wishes ==

=== MNG target filetype ===

The ability to save as/in the Free/Open MNG (.mng) format [http://libpng.org/pub/mng/]

A partial implementation was committed in SVN r470.

It was implemented in svn 986. See [[Render options]]. --[[User:Genete|Genete]] 13:12, 29 October 2007 (EDT)

=== Optionally display RGB in Hex in Color dialog ===

(3) When colors are quoted as 3 bytes of hexadecimal, you have to convert them to decimal, divide by 255, multiply by 100 to get a number to type into the dialog box. It's painful to match color schemes for example, with the [http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines Tango Icon Theme style guidelines]. [[User:pxegeek|PXEGeek]] 3/16/07

: Added in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=40dda9d27b5249ee32f62d84c819ff569f078929 svn r354]. You can type 3 or 6 digit hex codes and hit return to use. 3 digit code 36a gives colour 3366aa (each digit is duplicated) -- [[User:Dooglus|dooglus]] 3/18/07

:: Many thanks - already used many times! PXEGeek.

::: Did you notice that you can use single digit codes too? '5' gives 555555 for instance, giving you 16 equally spaces shades of black through white. -- [[User:Dooglus|dooglus]] 17:51, 25 September 2007 (EDT)

=== Restore Default Layout ===

(3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.
-> I'd like to second this one - especially with the bug where dialog boxes sometime shrink to nothing or offscreen, and no amount of maximizing or minimizing restores them. The only solution is to kill the windows, and none of the combo options in the dialog menu match the default configuration. 4/4/07 PXEGeek

: Implemented in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=036306f3c2c265a604971728d50fcce258766552 svn r757] -- [[User:Dooglus|dooglus]] 17:48, 25 September 2007 (EDT)

=== General outline / Polygon-based Outline / "Set Tangents to Zero" button ===
(3.5) I'm no artist, thus my primary form of art is stick figures, not to mention, many interesting animations are done in stick-figure style. Stick figures must be perfectly straight to get the effect across, so when I'm making an outline using B-Curves, it is too time consuming to set the tangents to 0 each time. Similarly, outlines of other shapes like squares, circles and so forth would be very useful. Whichever of the above is easiest, please implement right away. --[[User:Dragontamer|Dragontamer]] 02:35, 19 November 2007 (EST)
: For perfectly straight lines, click without moving the mouse. You will get a single point with no tangents. Outline shapes would require some development, particularly with some thought given to backward compatibility. A workaround you might consider is to create a duplicate shape with a different color and make the top one slightly smaller, so the outline of the one below shows. [[User:Pxegeek|Pxegeek]] 21:58, 19 November 2007 (EST)
:: Well, in general, whenever I click on a point to edit it (say, to make it move somewhere in animation mode), there is a decent chance that I click on a tangent instead. Then, if I want to right click the point itself, I usually right click the tangent marker instead. It isn't that big a deal, but simplicity at the cost of power generally is a good thing, especially when it will save a few mouse clicks.
:: As for the outlines, yeah, I've tried that and it is a decent solution for now, although it is no replacement for a real outline. I am going to also experiment with a clamp to see if I can make the center of the shape have 100% alpha... but I don't have synfig on the computer I'm on right now. Thanks for the tips Pxegeek. --[[User:Dragontamer|Dragontamer]] 01:58, 27 November 2007 (EST)
::: You can press Alt+3 to hide tangent ducks. --[[User:Zelgadis|Zelgadis]] 09:27, 27 November 2007 (EST)

=== Copy & Paste/Image Importing ===

(4) I sometimes make graphics in other programs, or use clipart and other images. Would it be possible for Synfig to be able to import images and/or copy and paste them?--Khlieeq 2007-07-19
Well, it doesn't support Copy & paste from the clipboard, but you can import images using "New Layer -> Other -> Import". This will create an Import layer, for which you can then edit the properties to point to the file containing your image. PXEGeek. 2007-07-19

=== Recursive Waypoint Manipulation ===

(4) it is really tiresome to revert changes to waypoints created by manipulating tangent/position ducks or change their interpolation functions. making it possible to right-click-modify the waypoint shown for objects that have some waypoint in a referenced sub-object would be great! -- timonator 2007-06-01
:You can do it in two ways: changing the interpolation method of the waypoint of paste canvas or editing the keyframe properties. The first allow to modify the waypoints interpolation method for all the waypoints of all the parameters of all the layers that are inside the paste canvas layer. You can right click on the left or right part of the waypoint to edit by a context menu the left or the right interpolation method of the waipoints. The second method would add and modify all the parameters that have any waypoint in the animation. See [[Keyframe]] for more detail. --[[User:Genete|Genete]] 13:10, 29 October 2007 (EDT)

=== Tweening for images developed in other imaging programs ===

It's obvious I am a beginner at image movement, but morphing is not enough: movement across the page is needed. Thanks for listening. [[User:Comwell@bellsouth.net|Comwell]] 
Imported images can be moved across the page. They can also be scaled, rotated and deformed. Was there a specific example you had in mind? [[User:Pxegeek|pxegeek]] 
:I also would like a way to tween images that have been drawn in other programs. I've had trouble drawing with Bline tool and the drawing tool in Synfig, and I'd rather just draw with a paint brush (like the one in Photoshop). Another problem I have is that Synfig tends to shut down on me every 20 minutes or so, and it's really frustrating even with the auto recover feature, because my sketches disappear. It'd be nice if I'm able to draw all of the keyframes in Photoshop or another image program and import it to Synfig so that Synfig can tween and animate them. Thank you. [[User:xychefoo@gmail.com|Huina]]
::You CAN use images, drawn in other programs. Just select "File->Import" from [[Canvas Menu Caret|canvas menu]] --[[User:Zelgadis|Zelgadis]] 01:39, 24 November 2007 (EST)
:::But how do you animate using images from other sources? I tried to make 2 keyframes with 2 different images, and it doesn't animate. It just stays as 1 picture for the entire render. The closest thing I saw to importing images from another source into Synfig and having it animate is the Walking Cycle Tutorial, but I would still have to trace the images to make it animate. As I said earlier, I'm not entirely fond of using the draw/Bline tool. [[User:xychefoo@gmail.com|Huina]]
:::: Huina, there's no way to do what you want right now. Interpolating between two images that are not created in Synfig is well beyond its scope right now. However, what you could do is take an image and separate elements of the picture onto different layers (e.g. have a picture of an arm and another of the rest of the body) and you can move those around, stretch and rotate them. (If you're familiar with the work of Terry Gilliam on Monty Python you'll know what I mean) I don't know how feasible it is to implement your request (I suspect some heavy lifting). We'll keep it on the list, but don't hold your breath. [[User:Pxegeek|Pxegeek]] 19:57, 24 November 2007 (EST)

:::: I think, you hardly find any other animation package which allow you to do such things. You could use a special tools for this task, like xmorph (http://xmorph.sourceforge.net/). But to do the tween between two bitmap images you STILL need to set points. It's not tracing, but very similar. Anyway, result may be poor and I'd better suggest to use technique, described in Walking Cycle Tutorial or which the [[User:Pxegeek|Pxegeek]] meant. --[[User:Zelgadis|Zelgadis]] 02:08, 25 November 2007 (EST)

:::: There is a technique called "optical flow". It takes two input frames and calculates the movement of each individual pixel between the frames, allowing interpolation to be done. Here's an example: http://www.fxguide.com/article333.html. It doesn't require setting of control points, but it has problems it's own set of problems: http://www.fxguide.com/article333.html. --[[User:Yoyobuae|Yoyobuae]] 13:32, 3 February 2008 (EST)

=== Auto-link option in [[Draw tool]] ===

(4) so that you can draw a line, and have its endpoint automatically link to a duck - or if Auto-connect is off, you can get a line object linked to the end of another line object. / I missed this too, it even should be like that by default I think. [[User:Maxy|Maxy]] 13:22, 25 Apr 2006 (PDT)

: Isn't this done already? We don't have line objects, but blines are automatically linked to if auto-connect is on. Am I missing something? -- [[User:Dooglus|dooglus]] 17:29, 27 September 2007 (EDT)

::To clarify dooglus' comments - If you have an outline created by the draw tool highlighted in the layer dialog and the auto-extend checkbox is checked, then you can continue drawing with the draw tool in that same layer. Blines created with the Bline tool cannot be extended once a different tool or layer is selected. [[User:Pxegeek|Pxegeek]] 23:46, 12 October 2007 (EDT)

::: A line is a line - Synfig doesn't remember whether it was created with the Bline tool or the Draw tool - so you can extend blines created with the bline tool using the draw tool. Just make sure the line is selected (so that its ducks are visible), not looped (so that it has end points to extend from), enable the draw tool, check 'auto extend' and start drawing at one of its end ducks. [[User:Dooglus|dooglus]] 05:47, 13 October 2007 (EDT)

So this sounds like it is already done. But on a related note, being able to open an existing bline in the bline tool to extend it would be useful. -- [[User:Dooglus|dooglus]] 04:51, 29 January 2008 (EST)

=== Layer hide boolean parameter ===

(3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Panel]], and builds upon it as well, allowing the [[Layers Panel]] to dynamically unclutter. ''(This feature request is a refactoring of the [[Amount Parameter]])''
: With the addition of the [[Convert#Switch|Switch]] type conversion it is not needed this feature request. You can convert the Amount parameter to a Switch value and give 0 and 1 to the Linked OFF/ON values. --[[User:Genete|Genete]] 13:20, 29 October 2007 (EDT)

=== Riding ducks ===

(2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.
:Already done in SVN.[[User:Genete|Genete]] 18:59, 5 April 2008 (EDT)

=== Image filmstrip import ===

(2) — Allow import of a series of images (TGA, etc) as frames of an animation, on a layer. 
Response - 'lst' files of a list of images can be imported. I've used this to develop a walk cycle. See [[Walk_Cycle|Walk cycle]] for an example. [[user:pxegeek|pxegeek]]

=== Character Animation Tools ===

I have seen some interesting methods for helping character design/animation in different 2d/3d software. Hash's animation master has 'poses' which are extremes of a model, for example smiling and frowning, once you add these extremes ot a set you can use slider to create a pose that somewhere inbetween. The real power of this is when you have serveral different poses on the same object, a face say, you can easily come up with new facial expressions. Maybe something similar could be done with synfig using layers and groups, the implementation could something similar to Moho's switch layers. --[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)
: Have you read this tutorial? [[Reuse Animations]]. It is very close to the Switch layer of Moho/Anime Studio. Also You can change the Canvas parameter to any other canvas dynamically in the time line by clicking on it and selecting other exported canvas. Other option is convert the canvas to a Switch type and alternate between two different canvas. --[[User:Genete|Genete]] 13:26, 29 October 2007 (EDT)

=== More Animation Tools ===

[[New Animation Tools|Added here]]

=== Improved User Experience for First Contact ===
* Single file download and installer (at least for Windows)
* Ability to draw the first object directly after starting the application (start with an empty document)
* Ability to animate the object directly after drawing the first object (new documents have a say 3 seconds timeline)
In my opinion this is crucial to attract potential users. Because if I see how easy it is to create my first animation I'm going to accept all the bugs and clumsyness. A good example is the Pencil animation software. --[[User:Dmd|Dmd]] 13:50, 26 January 2008 (EST)

: I've implemented #2 and #3 above in svn r1519 & 1520. If no files are specified to be opened when running studio, it'll make a new one. It won't pop up the canvas properties dialog when making new canvases by default. And the default end time is 5s (3s is small enough to cause the time slider to show "1s 12f", whereas 5s looks cleaner). -- [[User:Dooglus|dooglus]] 04:00, 29 January 2008 (EST)

=== Automatic attach and manipulate a Vertex to a Bline ===

Please see [[Inverse Duck Manipulation|this]] page to understand what we want. --[[User:Genete|Genete]] 12:43, 3 March 2008 (EST).
:Already done in SVN. [[User:Genete|Genete]] 19:00, 5 April 2008 (EDT)

=== Toggle visible ducks ===
(3) So pressing, say, tab while editing a Bline toggles which vertices/ducks are visible - so we can easily move the actual vertices around without having the view cluttered by tangeants (and also make it easier to select 'Loop' rather than 'Split Tangeants' when creating the thing.)

Given that extra ducks such as the width ones listed above may be added, this might become more and more necessary. If too many different sets are added for toggling to be feasible, each visibility for each set can be hotkeyed.

: Synfig already have hotkeys to toggle visibility of the ducks. See [[Keyboard_Shortcuts#Hotkeys_Visual_Guide]]. --[[User:Zelgadis|Zelgadis]] 00:39, 22 April 2008 (EDT)

Doc:How Do I

2009-01-07T22:04:40Z

Creek23: /* Apply a gradient to an object instead of the entire canvas? */ added changing shorcut keys

[[Category:Tutorials]]

Feel free to add your own questions here or [[Contact|contact]] us with them. Or put them on the [[Wiki Wish List]].

__TOC__

== Insert some text? ==

With recent development versions, there is a text tool. If you are using 0.61.08 or earlier, use right click on your canvas and choose Layer > New > Other > Text.

== How to change shortcut keys? ==
'''1.''' Find your Synfig config file under:
''Ubuntu GNU/Linux:'' /home/{username}/Synfig/
''Windows XP:'' C:\Documents and Settings\{username}\Synfig\
''Windows Vista:'' C:\Users\{username}\Synfig\
'''2.''' Open the file, named '''accelrc''', using any text editing software (GEdit, Kate, Notepad).
'''3.''' Change the shorcuts you want, save and close.

== How to have a Flash-like shorcut keys ==
'''1.''' Follow the step on how to change shortcut keys, except for step 3.
'''2.''' Copy the code below and paste it on the very last part of '''accelrc''' then save and close it.
<code>
; misc
(gtk_accel_path "<Actions>//redo" "<Control>y")
; tools
(gtk_accel_path "<Actions>//state-text" "t")
(gtk_accel_path "<Actions>//state-rectangle" "r")
(gtk_accel_path "<Actions>//state-rotate" "<Shift>q")
(gtk_accel_path "<Actions>//state-zoom" "z")
(gtk_accel_path "<Actions>//state-polygon" "n")
(gtk_accel_path "<Actions>//state-bline" "p")
(gtk_accel_path "<Actions>//state-normal" "v")
(gtk_accel_path "<Actions>//state-eyedrop" "i")
(gtk_accel_path "<Actions>//state-fill" "k")
(gtk_accel_path "<Actions>//state-circle" "o")
(gtk_accel_path "<Actions>//state-scale" "q")
(gtk_accel_path "<Actions>//state-gradient" "g")
; navigation
(gtk_accel_path "<Actions>//seek-next-frame" "period")
(gtk_accel_path "<Actions>//seek-prev-frame" "comma")
</code>

== Apply a gradient to an object instead of the entire canvas? ==

# Create the region you want to fill with a gradient, and the gradient layer, if you haven't already.
# Make sure that the gradient layer is above the region layer in the [[Layers Panel]].
# Select both layers, right click, and select [[Encapsulate]].
# Expand the new [[Paste Canvas|Inline Canvas]] layer if it's not already, and select your gradient layer.
# In the [[Params Panel]] select the [[Blend Method]] parameter, and choose [[Blend Method#Onto|Onto]] from the drop-down menu.

The gradient will clip to the visible area of the region below it inside the [[Paste Canvas|Inline Canvas]]. (and any other layers in that section).

== Show or hide a layer, or fade the effect of a blur? ==
In the [[Params Panel]], look for an option labeled [[Amount Parameter|Amount]] - this controls how much of the blended result of the layer is composited with the blend of the layers beneath it.

In other words, for a typical layer, this will 'fade it out'. For a [[Blur Layer]] set to "[[Blend Method#Straight|Straight]]", this will fade ''between'' the blurred version and the unblurred version of the canvas. If you want it to become less blurry, adjust the [[Blur Layer#Size|Blur Layer's 'size' parameter]].

== Fill an outline? ==
(Requested by [[User:Karlb|Karlb]])

There are several options:
* The easiest way is to link a new region layer to the outline's shape.
*# Select the outline you want to fill.
*# In the Params Panel, right-click the Vertices parameter, select "Export", enter a name for the shape, and hit return. This will export the shape of the outline, making it visible in the Children dialog.
*# In the Children dialog, open the ValueBase Nodes tree and select the name you just saved the shape as.
*# From the [[Layer Menu]] (either context-click on the [[Layers Panel]] or use the [[Canvas Menu Caret]]) create a new [[Region Layer]] by selecting "New Layer -> Geometry -> Region". Ensure that the created layer is selected.
*# In the parameter dialog, right-click the Vertices parameter and click "Connect".
*# Now, if you don't need exported shape, you can unexport it: right click name of the shape in the Children dialog and click "Unexport".
* Similar to the above, but using a different method:
*# Create a new region layer as above, and leave it selected.
*# Don't make any changes to the outline layer, which you want to fill! (see the Tier 5 on the [[Linking]] page for details).
*# Select both layers in the [[Layers Panel]] This will display only the parameters shared by both layers in the [[Params Panel]].
*# Context-click on the [[Vertices Parameter]], and select [[Linking|Link]].
*# The [[Region Layer]] will snap to the shape of the [[Outline Layer]].
* When you create an [[Outline Layer|outline]] with the [[Bline Tool]] that you intend to be a filled area as well, make sure you select the Fill checkbox in the [[Bline Tool#Options|tool options dialog]]. Obviously, this doesn't help much if you realise later that you needed a fill here.
* If you are using the [[draw tool]], there is a button at the bottom of the [[draw tool#Options|tool options dialog]] labeled "Fill Last Stroke", which creates a new [[Region Layer]] and links its shape to the previously drawn outline. Unfortunately, it doesn't work as of Synfig Studio v0.61.04. It has been fixed in the current SVN version of the code.
* Create a [[Region Layer|region]] with the same number of ducks, and manually link each duck. If you want a region that depends on multiple outline layers, this is really your only choice for now.
* Use the draw tool, select only the outline to fill, draw a stroke roughly following the outline and make sure you're holding the Control key when you left go of the mouse button at the end of the stroke. This doesn't work 100% right at the moment.

== Dock windows together? ==

*To dock (join) separate windows into one you must drag the tab ''icons'' for each of the tools into another window.
*You can create subdivisions inside the windows by dragging the icons into the side tabs (located around the edges, the look like rectangles).
*Tool tabs inside the window can be arranged by dragging them on top of one another, therefore changing the order.
*''How Do I min/maximize all Synfig windows on a Windows pc''? There must be an easy way/tool to do this?

== Use an external bitmap? ==

* In the image menu (>) choose file-->import. PNG with alpha channel works fine.
* To animate it without accidental stretching, right-click on the layer and choose encapsulate. You can then animate the position of the new "Inline Canvas" layer instead of the bbox.

== Use an image as a fill colour? ==

Make a new object (bline, region, squares, circles, polygons all work)
Import the image you want as the fill colour, and put it on the layer underneith your object. Set the blend method of the image (using the [[Parameters Palette]]) to "onto" or "straightonto".
Encapsulate the object and the fill colour image, otherwise everthing below the image will have the same fill colour.
Be sure to have a look at what the other composite options do as well.

== Use an external Vector? ==

Synfig doesn't yet support vector import because no-one has written an import process yet. You can use the Svg2synfig [[Converters|converter]], or import it as a bitmap and trace over it in synfig. If you want to implement vector import we would gladly accept your patch.

== Close a bline? ==

* Right click on the starting point and then click on loop bline.

Note: It doesn't work unless the initial point has a tangent - ie the first segment is curved. But you can hide tangent ducks (Alt+3, or "Caret Menu > View > Show/Hide Ducks > Show tangent ducks") and process as described. Don't forget to press (Alt+3) after that to show tangent ducks again.

== How do I transform encapsulated objects? ==

* Right click on the Encapsulated object in the Layer dialog and choose "select all child layers". Then you select the ducks you want to transform (usually just all of them, like for rotating the object), and the rotate or scale tool and do the work.

== Make objects go behind each other, without moving layers? ==

You'll notice each layer you make has a number in the z depth column in the Layers Panel. Say you have 3 layers, they will be numbered 2 (lowest, e.g. a square) 1 (eg a circle) 0 (highest, the default, e.g. a line). In order to make layer 1, the circle, pass behind layer 2, the square, change its z depth to be 3 or more. The z depth of the circle needs to be greater than 2 in order to be behind the square. To make the square on top of everything, you'd change its z depth to -1 or less.

Positive numbers on the z axis go into the screen, and negative numbers go out of the screen, towards the viewer.

It is possible to animate this effect, but each layer is discrete. They seem to go from 0 to 0.9999.

In addition, objects in encapsulated layers can only go behind other objects in the same encapsulated layer. However an encapsulated layer can go behind another encapsulated layer.

== Copy a complex convert combination between parameters of different layers? ==

For example: you want to copy a complicated [[Convert|conversion]] type that you have in one parameter from a layer, to other parameter (maybe not a root parameter, but a sub-parameter) of other layer. If you [[Export|export]] the complicated conversion type from the original layer and then go to the other layer and select [[Connect]] (right click and the exported and the parameter both selected) then you have the parameter form the second layer to be exactly the same than the original one. But there is a drawback: if you modify one of the sub-parameters in the complicated conversion type (e.g. you change the value of one of them) then automatically the same sub-parameter of the other layer is changed.

How can you copy the conversion but allow modify the sub-parameters independently on each layer?

Once you have achieved the complex conversion type in the original layer, don't export the root parameter! If you have done yet [[Export|unexport]] it. (Why?. You will understand it later.) Now duplicate the original layer. Then you should obtain the same layer with the same conversion type placed at the same parameter (but not exported). NOW export the parameter from the duplicated layer. Then go to the (sub) parameter of the layer where you want to copy the complex conversion type and Connect it to the just exported parameter form the duplicated layer. Now delete the duplicated layer (!). Then the exported [[ValueNode]] still undeleted and the layer where you wanted to copy the complex convert type have a (sub) parameter connected to it. You can [[Export|unexport]] the ValueNode or not. It is up to you. But notice that the conversion type is already copied into other (sub) parameter of other layer and they are independent as well as you can change one of them (by modifying the sub-parameters) and the other remains untouched.

== Make an existing animation run at half speed? ==

If you have an animation that runs from 0s to 10s and you want it to run at half speed from 0s to 20s, how can you do that?

* Either: encapsulate it, and use the 'time offset' parameter in the encapsulation layer to slow it down:
** Right-click 'time offset' in the encapsulation layer, convert>linear, rate -0.5 offset 0. That means offset the time by -0.5 seconds per second - or in other words, run at half speed
** Or, putting waypoints on the 'time offset' param would work too: 0 at 0s and -10 at 20s. (The choice between using a linear convert and valuenodes is entirely up to you. They both achieve the same result in this simple case).

* Or: use a [[Time Loop Layer]]. The first method seems better and more intuitive in this case, but there are ways of getting the same effect from the Time Loop layer. Perhaps the Time Loop layer is better if the animation doesn't run from 0s, but from some other time. Anyway: put a Time Loop layer over the layers you wish to slow down, and:
** Either: set duration to 0, local time to 0, convert->linear the link time and set rate to 0.5 - this slows the animation down *to* 50% of its original speed; use bigger rates to slow it down less
** Or: set duration to 1h (*), link time to 0, convert->linear the local time and set rate to 0.5 - this slows the animation down *by* 50%; use bigger rates to slow it down more
(*) if your animation is longer than 1h then set this parameter to EOT (End Of Time) what is the same as Infinite (INF) for a real number but for a time parameter.

== Draw a rectangle with a given width and height? ==

I was asked on IRC how to specify the width and height of a rectangle, rather than having to specify the position of two opposite corners. Here's how:

* draw a rectangle
* go to the [[Params Panel]]
* right-click the 'point 1' parameter and [[Export]]
* give it a name, "p1" say
* right-click the 'point 2' parameter and [[Convert]] to [[Convert#Add|Add]]
* (that's saying that rather than specifying the absolute position of the other point, you want synfig to calculate it for you)
* (it will make 2 new sub-parameters for 'point 2', and the value used for point 2 will be their sum so we want to tell it to use 'point 1' and your (width,height))
* open up the sub-parameters of 'point 2' by clicking the triangle to its left
* go to the [[Children Panel]], open up the values and select the one you exported earlier (p1)
* right-click the "LHS" parameter in the parameters dialog and [[Connect]] it
* then enter the width and height you want in the 'RHS' parameter

== Make linked BLine vertices not affected by Rotate layer? ==
Look at the http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-02-07.log
See also: [[Convert]].

== Create dashed outlines? ==

If you want to make simple dashed outlines the faster way is proceed like this:

* Create a Curve Gradient and an Outline over the same [[Bline]] using the [[Bline Tool]] options. Check both Outline and Gradient at the [[Tool Options Panel]].
* Raise up the gradient layer (it is created below the [[Outline Layer]]).
* Modify the gradient [[Blend Method]] parameter to be Straight Onto. That would render the gradient onto the outline width. Also it wouldn't render the outline, so transparent portions of the gradient are transparent.
* Check the 'Perpendicular' parameter of the Curve Gradient Layer.
* [[Convert]] the Gradient Parameter of the Curve Gradient Layer to be one of those types: Stripes or Repeat Gradient.
* Modify the properties of the sub parameters to achieve the desired effect.

== Render to AVI with higher quality? ==

=== Using raw video ===
The module used by Synfig to render AVI files is ffmpeg. For the moment there is not interface to control ffmpeg options so you render with a fixed bitrate and quality. If you want the maximum quality in your AVI file, follow these steps:

* Render your animation to yuv420p format. To do that select that target at the drop down list of the render dialog and add the ".yuv" extension to your animation name (without quotes).
* Once rendered (it would produce a huge size yuv file) you can quickly convert it to AVI using this command:

ffmpeg -i animation.yuv -sameq animation.avi

Change the animation file name to your one.

=== Rendering trough png sequence. ===
Render your sif to png sequence
mkdir render
synfig my_animation.sifz -o render/frame.png
Then convert it to movie with ffmpeg
ffmpeg -r <frame rate> -i render/frame.%04d.png <more settings from ffmpeg's manual> my_animation.mov
If you need nice open source format without any tweaks you may try ffmpeg2theora:
ffmpeg2theora render/frame.%04d.png --inputfps <frame rate> -o my_animation.ogg
png takes less disk space then yuv.
--[[User:AkhIL|AkhIL]] 21:38, 9 April 2008 (EDT)

==Increase performance by optimizing during compilation time? ==

I would like to know what parameters do I need to apply to configure to improve performance. [[User:Genete|Genete]] 11:04, 9 April 2008 (EDT)

To optimize program you should set two environment variables
export CFLAGS=""
export CXXFLAGS=$CFLAGS

First flag will be "-O3" (ow three). "-02" is normal optimization. "-03" is hard optimisation.

Now you should get info about your CPU
cat /proc/cpuinfo

find your cpu model name

now go to man gcc and searc "-mtune"

find your cpu and add "-mtune=your-cpu -march=your-cpu" to CFLAGS.

Then look at flags from /proc/cpuinfo and search it in gcc manual
For example I have 3dnow. So I can find "-m3dnow". For sse I can find "-msse" and "-mfpmath=sse" (can make program unstable).

Finaly you may add "-ffast-math" to disable math checks. But it can make program unstable.

For my AthlonXP I'm using this flags:
export CFLAGS="-O3 -pipe -mtune=athlon-xp -march=athlon-xp -mmmx -msse -m3dnow -mfpmath=sse -ffast-math -funsigned-char -fno-strict-aliasing"
export CXXFLAGS=$CFLAGS
--[[User:AkhIL|AkhIL]] 12:05, 9 April 2008 (EDT)

For my Pentium3 i use the line:
export CFLAGS="-O3 -pipe -mtune=pentium3 -march=pentium3 -msse -mfpmath=sse -funsigned-char -fno-strict-aliasing"
export CXXFLAGS=$CFLAGS

The additional switches -mmmx and -ffast-math does seem to '''not''' yield any gain in computing performance! So you could leave them out.
--[[User:SvH|SvH]] 03:46, 20 May 2008 (EDT)

== Import a movie into Synfig? ==

To import a movie (image only, not sound) into synfig there is only one option for the moment: Extract an image sequence from the movie and import them using [[ListImporter]]. Before you can load the image sequence you have to extract it from the movie. There are several software to do that but a straight and easy way is to use mplayer:

mplayer mymovie.avi -vo png:z=1 -ss seconds-start -endpos duration

where ''seconds-start'' are the seconds where you want to extract form and ''duration'' is the number of seconds you want to extract from ''mymovie.avi''. Also the image format specified in this case is png but jpeg or tga can be used also. See [http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html mplayer manual page] for more info.

It would extract a set of files of the selected section of the movie. Each file takes the frame number padded with leading zeros as name.

To put all the filenames into a ''.lst'' file just type this in the folder wehre the files are:

ls *.png >> mymovie.lst

and add a line specifying the frame rate at the beginning of the text file:

FPS 25

if the movie was 25 fps.

== Granted Wishes ==

=== MNG target filetype ===

The ability to save as/in the Free/Open MNG (.mng) format [http://libpng.org/pub/mng/]

A partial implementation was committed in SVN r470.

It was implemented in svn 986. See [[Render options]]. --[[User:Genete|Genete]] 13:12, 29 October 2007 (EDT)

=== Optionally display RGB in Hex in Color dialog ===

(3) When colors are quoted as 3 bytes of hexadecimal, you have to convert them to decimal, divide by 255, multiply by 100 to get a number to type into the dialog box. It's painful to match color schemes for example, with the [http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines Tango Icon Theme style guidelines]. [[User:pxegeek|PXEGeek]] 3/16/07

: Added in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=40dda9d27b5249ee32f62d84c819ff569f078929 svn r354]. You can type 3 or 6 digit hex codes and hit return to use. 3 digit code 36a gives colour 3366aa (each digit is duplicated) -- [[User:Dooglus|dooglus]] 3/18/07

:: Many thanks - already used many times! PXEGeek.

::: Did you notice that you can use single digit codes too? '5' gives 555555 for instance, giving you 16 equally spaces shades of black through white. -- [[User:Dooglus|dooglus]] 17:51, 25 September 2007 (EDT)

=== Restore Default Layout ===

(3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.
-> I'd like to second this one - especially with the bug where dialog boxes sometime shrink to nothing or offscreen, and no amount of maximizing or minimizing restores them. The only solution is to kill the windows, and none of the combo options in the dialog menu match the default configuration. 4/4/07 PXEGeek

: Implemented in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=036306f3c2c265a604971728d50fcce258766552 svn r757] -- [[User:Dooglus|dooglus]] 17:48, 25 September 2007 (EDT)

=== General outline / Polygon-based Outline / "Set Tangents to Zero" button ===
(3.5) I'm no artist, thus my primary form of art is stick figures, not to mention, many interesting animations are done in stick-figure style. Stick figures must be perfectly straight to get the effect across, so when I'm making an outline using B-Curves, it is too time consuming to set the tangents to 0 each time. Similarly, outlines of other shapes like squares, circles and so forth would be very useful. Whichever of the above is easiest, please implement right away. --[[User:Dragontamer|Dragontamer]] 02:35, 19 November 2007 (EST)
: For perfectly straight lines, click without moving the mouse. You will get a single point with no tangents. Outline shapes would require some development, particularly with some thought given to backward compatibility. A workaround you might consider is to create a duplicate shape with a different color and make the top one slightly smaller, so the outline of the one below shows. [[User:Pxegeek|Pxegeek]] 21:58, 19 November 2007 (EST)
:: Well, in general, whenever I click on a point to edit it (say, to make it move somewhere in animation mode), there is a decent chance that I click on a tangent instead. Then, if I want to right click the point itself, I usually right click the tangent marker instead. It isn't that big a deal, but simplicity at the cost of power generally is a good thing, especially when it will save a few mouse clicks.
:: As for the outlines, yeah, I've tried that and it is a decent solution for now, although it is no replacement for a real outline. I am going to also experiment with a clamp to see if I can make the center of the shape have 100% alpha... but I don't have synfig on the computer I'm on right now. Thanks for the tips Pxegeek. --[[User:Dragontamer|Dragontamer]] 01:58, 27 November 2007 (EST)
::: You can press Alt+3 to hide tangent ducks. --[[User:Zelgadis|Zelgadis]] 09:27, 27 November 2007 (EST)

=== Copy & Paste/Image Importing ===

(4) I sometimes make graphics in other programs, or use clipart and other images. Would it be possible for Synfig to be able to import images and/or copy and paste them?--Khlieeq 2007-07-19
Well, it doesn't support Copy & paste from the clipboard, but you can import images using "New Layer -> Other -> Import". This will create an Import layer, for which you can then edit the properties to point to the file containing your image. PXEGeek. 2007-07-19

=== Recursive Waypoint Manipulation ===

(4) it is really tiresome to revert changes to waypoints created by manipulating tangent/position ducks or change their interpolation functions. making it possible to right-click-modify the waypoint shown for objects that have some waypoint in a referenced sub-object would be great! -- timonator 2007-06-01
:You can do it in two ways: changing the interpolation method of the waypoint of paste canvas or editing the keyframe properties. The first allow to modify the waypoints interpolation method for all the waypoints of all the parameters of all the layers that are inside the paste canvas layer. You can right click on the left or right part of the waypoint to edit by a context menu the left or the right interpolation method of the waipoints. The second method would add and modify all the parameters that have any waypoint in the animation. See [[Keyframe]] for more detail. --[[User:Genete|Genete]] 13:10, 29 October 2007 (EDT)

=== Tweening for images developed in other imaging programs ===

It's obvious I am a beginner at image movement, but morphing is not enough: movement across the page is needed. Thanks for listening. [[User:Comwell@bellsouth.net|Comwell]] 
Imported images can be moved across the page. They can also be scaled, rotated and deformed. Was there a specific example you had in mind? [[User:Pxegeek|pxegeek]] 
:I also would like a way to tween images that have been drawn in other programs. I've had trouble drawing with Bline tool and the drawing tool in Synfig, and I'd rather just draw with a paint brush (like the one in Photoshop). Another problem I have is that Synfig tends to shut down on me every 20 minutes or so, and it's really frustrating even with the auto recover feature, because my sketches disappear. It'd be nice if I'm able to draw all of the keyframes in Photoshop or another image program and import it to Synfig so that Synfig can tween and animate them. Thank you. [[User:xychefoo@gmail.com|Huina]]
::You CAN use images, drawn in other programs. Just select "File->Import" from [[Canvas Menu Caret|canvas menu]] --[[User:Zelgadis|Zelgadis]] 01:39, 24 November 2007 (EST)
:::But how do you animate using images from other sources? I tried to make 2 keyframes with 2 different images, and it doesn't animate. It just stays as 1 picture for the entire render. The closest thing I saw to importing images from another source into Synfig and having it animate is the Walking Cycle Tutorial, but I would still have to trace the images to make it animate. As I said earlier, I'm not entirely fond of using the draw/Bline tool. [[User:xychefoo@gmail.com|Huina]]
:::: Huina, there's no way to do what you want right now. Interpolating between two images that are not created in Synfig is well beyond its scope right now. However, what you could do is take an image and separate elements of the picture onto different layers (e.g. have a picture of an arm and another of the rest of the body) and you can move those around, stretch and rotate them. (If you're familiar with the work of Terry Gilliam on Monty Python you'll know what I mean) I don't know how feasible it is to implement your request (I suspect some heavy lifting). We'll keep it on the list, but don't hold your breath. [[User:Pxegeek|Pxegeek]] 19:57, 24 November 2007 (EST)

:::: I think, you hardly find any other animation package which allow you to do such things. You could use a special tools for this task, like xmorph (http://xmorph.sourceforge.net/). But to do the tween between two bitmap images you STILL need to set points. It's not tracing, but very similar. Anyway, result may be poor and I'd better suggest to use technique, described in Walking Cycle Tutorial or which the [[User:Pxegeek|Pxegeek]] meant. --[[User:Zelgadis|Zelgadis]] 02:08, 25 November 2007 (EST)

:::: There is a technique called "optical flow". It takes two input frames and calculates the movement of each individual pixel between the frames, allowing interpolation to be done. Here's an example: http://www.fxguide.com/article333.html. It doesn't require setting of control points, but it has problems it's own set of problems: http://www.fxguide.com/article333.html. --[[User:Yoyobuae|Yoyobuae]] 13:32, 3 February 2008 (EST)

=== Auto-link option in [[Draw tool]] ===

(4) so that you can draw a line, and have its endpoint automatically link to a duck - or if Auto-connect is off, you can get a line object linked to the end of another line object. / I missed this too, it even should be like that by default I think. [[User:Maxy|Maxy]] 13:22, 25 Apr 2006 (PDT)

: Isn't this done already? We don't have line objects, but blines are automatically linked to if auto-connect is on. Am I missing something? -- [[User:Dooglus|dooglus]] 17:29, 27 September 2007 (EDT)

::To clarify dooglus' comments - If you have an outline created by the draw tool highlighted in the layer dialog and the auto-extend checkbox is checked, then you can continue drawing with the draw tool in that same layer. Blines created with the Bline tool cannot be extended once a different tool or layer is selected. [[User:Pxegeek|Pxegeek]] 23:46, 12 October 2007 (EDT)

::: A line is a line - Synfig doesn't remember whether it was created with the Bline tool or the Draw tool - so you can extend blines created with the bline tool using the draw tool. Just make sure the line is selected (so that its ducks are visible), not looped (so that it has end points to extend from), enable the draw tool, check 'auto extend' and start drawing at one of its end ducks. [[User:Dooglus|dooglus]] 05:47, 13 October 2007 (EDT)

So this sounds like it is already done. But on a related note, being able to open an existing bline in the bline tool to extend it would be useful. -- [[User:Dooglus|dooglus]] 04:51, 29 January 2008 (EST)

=== Layer hide boolean parameter ===

(3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Panel]], and builds upon it as well, allowing the [[Layers Panel]] to dynamically unclutter. ''(This feature request is a refactoring of the [[Amount Parameter]])''
: With the addition of the [[Convert#Switch|Switch]] type conversion it is not needed this feature request. You can convert the Amount parameter to a Switch value and give 0 and 1 to the Linked OFF/ON values. --[[User:Genete|Genete]] 13:20, 29 October 2007 (EDT)

=== Riding ducks ===

(2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.
:Already done in SVN.[[User:Genete|Genete]] 18:59, 5 April 2008 (EDT)

=== Image filmstrip import ===

(2) — Allow import of a series of images (TGA, etc) as frames of an animation, on a layer. 
Response - 'lst' files of a list of images can be imported. I've used this to develop a walk cycle. See [[Walk_Cycle|Walk cycle]] for an example. [[user:pxegeek|pxegeek]]

=== Character Animation Tools ===

I have seen some interesting methods for helping character design/animation in different 2d/3d software. Hash's animation master has 'poses' which are extremes of a model, for example smiling and frowning, once you add these extremes ot a set you can use slider to create a pose that somewhere inbetween. The real power of this is when you have serveral different poses on the same object, a face say, you can easily come up with new facial expressions. Maybe something similar could be done with synfig using layers and groups, the implementation could something similar to Moho's switch layers. --[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)
: Have you read this tutorial? [[Reuse Animations]]. It is very close to the Switch layer of Moho/Anime Studio. Also You can change the Canvas parameter to any other canvas dynamically in the time line by clicking on it and selecting other exported canvas. Other option is convert the canvas to a Switch type and alternate between two different canvas. --[[User:Genete|Genete]] 13:26, 29 October 2007 (EDT)

=== More Animation Tools ===

[[New Animation Tools|Added here]]

=== Improved User Experience for First Contact ===
* Single file download and installer (at least for Windows)
* Ability to draw the first object directly after starting the application (start with an empty document)
* Ability to animate the object directly after drawing the first object (new documents have a say 3 seconds timeline)
In my opinion this is crucial to attract potential users. Because if I see how easy it is to create my first animation I'm going to accept all the bugs and clumsyness. A good example is the Pencil animation software. --[[User:Dmd|Dmd]] 13:50, 26 January 2008 (EST)

: I've implemented #2 and #3 above in svn r1519 & 1520. If no files are specified to be opened when running studio, it'll make a new one. It won't pop up the canvas properties dialog when making new canvases by default. And the default end time is 5s (3s is small enough to cause the time slider to show "1s 12f", whereas 5s looks cleaner). -- [[User:Dooglus|dooglus]] 04:00, 29 January 2008 (EST)

=== Automatic attach and manipulate a Vertex to a Bline ===

Please see [[Inverse Duck Manipulation|this]] page to understand what we want. --[[User:Genete|Genete]] 12:43, 3 March 2008 (EST).
:Already done in SVN. [[User:Genete|Genete]] 19:00, 5 April 2008 (EDT)

=== Toggle visible ducks ===
(3) So pressing, say, tab while editing a Bline toggles which vertices/ducks are visible - so we can easily move the actual vertices around without having the view cluttered by tangeants (and also make it easier to select 'Loop' rather than 'Split Tangeants' when creating the thing.)

Given that extra ducks such as the width ones listed above may be added, this might become more and more necessary. If too many different sets are added for toggling to be feasible, each visibility for each set can be hotkeyed.

: Synfig already have hotkeys to toggle visibility of the ducks. See [[Keyboard_Shortcuts#Hotkeys_Visual_Guide]]. --[[User:Zelgadis|Zelgadis]] 00:39, 22 April 2008 (EDT)

Keyboard Shortcuts (Flash)

2009-01-07T21:58:04Z

Creek23: /* How to have a Flash-like shorcut keys in Synfig? */

=== How to have a Flash-like shortcut keys in Synfig? ===
This is how you can make a Flash-like shortcut keys in Synfig.

'''NOTE:''' You must have Synfig installed and run at least once. :D

'''1.''' Find your Synfig config file under:
''Ubuntu GNU/Linux:'' /home/{username}/Synfig/
''Windows XP:'' C:\Documents and Settings\{username}\Synfig\
''Windows Vista:'' C:\Users\{username}\Synfig\
'''2.''' Open the file, named '''accelrc''', using any text editing software (GEdit, Kate, Notepad).

'''3.''' Copy the code below and paste it on the very last part of '''accelrc'''.
<code>
; misc
(gtk_accel_path "<Actions>//redo" "<Control>y")
; tools
(gtk_accel_path "<Actions>//state-text" "t")
(gtk_accel_path "<Actions>//state-rectangle" "r")
(gtk_accel_path "<Actions>//state-rotate" "<Shift>q")
(gtk_accel_path "<Actions>//state-zoom" "z")
(gtk_accel_path "<Actions>//state-polygon" "n")
(gtk_accel_path "<Actions>//state-bline" "p")
(gtk_accel_path "<Actions>//state-normal" "v")
(gtk_accel_path "<Actions>//state-eyedrop" "i")
(gtk_accel_path "<Actions>//state-fill" "k")
(gtk_accel_path "<Actions>//state-circle" "o")
(gtk_accel_path "<Actions>//state-scale" "q")
(gtk_accel_path "<Actions>//state-gradient" "g")
; navigation
(gtk_accel_path "<Actions>//seek-next-frame" "period")
(gtk_accel_path "<Actions>//seek-prev-frame" "comma")
</code>
'''4.''' Save it, and run Synfig to test and enjoy!

=== How to restore to default settings? ===
Simply, delete '''accelrc''' and run Synfig.

Keyboard Shortcuts (Flash)

2009-01-07T21:33:17Z

Creek23: re-arranged accels

=== How to have a Flash-like shorcut keys in Synfig? ===
This is how you can make a Flash-like shortcut keys in Synfig.

'''NOTE:''' You must have Synfig installed and run at least once. :D

'''1.''' Find your Synfig config file under:
''Ubuntu GNU/Linux:'' /home/{username}/Synfig/
''Windows XP:'' C:\Documents and Settings\{username}\Synfig\
''Windows Vista:'' C:\Users\{username}\Synfig\
'''2.''' Open the file, named '''accelrc''', using any text editing software (GEdit, Kate, Notepad).

'''3.''' Copy the code below and paste it on the very last part of '''accelrc'''.
<code>
; misc
(gtk_accel_path "<Actions>//redo" "<Control>y")
; tools
(gtk_accel_path "<Actions>//state-text" "t")
(gtk_accel_path "<Actions>//state-rectangle" "r")
(gtk_accel_path "<Actions>//state-rotate" "<Shift>q")
(gtk_accel_path "<Actions>//state-zoom" "z")
(gtk_accel_path "<Actions>//state-polygon" "n")
(gtk_accel_path "<Actions>//state-bline" "p")
(gtk_accel_path "<Actions>//state-normal" "v")
(gtk_accel_path "<Actions>//state-eyedrop" "i")
(gtk_accel_path "<Actions>//state-fill" "k")
(gtk_accel_path "<Actions>//state-circle" "o")
(gtk_accel_path "<Actions>//state-scale" "q")
(gtk_accel_path "<Actions>//state-gradient" "g")
; navigation
(gtk_accel_path "<Actions>//seek-next-frame" "period")
(gtk_accel_path "<Actions>//seek-prev-frame" "comma")
</code>
'''4.''' Save it, and run Synfig to test and enjoy!

=== How to restore to default settings? ===
Simply, delete '''accelrc''' and run Synfig.

Keyboard Shortcuts (Flash)

2009-01-07T21:12:10Z

Creek23: -the

This is how you can make a Flash-like shortcut keys of the Synfig tools.

1. You must have Synfig installed and run at least once. :D
2. Find your Synfig config file under:
a.) ''Ubuntu GNU/Linux:'' /home/{username}/Synfig/
b.) ''Windows XP:'' C:\Documents and Settings\{username}\Synfig\
c.) ''Windows Vista:'' C:\Users\{username}\Synfig\
3. Open the file, named '''accelrc''', using any text editing software (GEdit, Kate, Notepad).
4. Copy the code below and paste it on the very last part of '''accelrc'''.
<code>
(gtk_accel_path "<Actions>//state-text" "t")
(gtk_accel_path "<Actions>//state-rectangle" "r")
(gtk_accel_path "<Actions>//state-rotate" "<Shift>q")
(gtk_accel_path "<Actions>//seek-next-frame" "period")
(gtk_accel_path "<Actions>//state-zoom" "z")
(gtk_accel_path "<Actions>//state-polygon" "n")
(gtk_accel_path "<Actions>//state-bline" "p")
(gtk_accel_path "<Actions>//state-normal" "v")
(gtk_accel_path "<Actions>//state-eyedrop" "i")
(gtk_accel_path "<Actions>//state-fill" "k")
(gtk_accel_path "<Actions>//state-circle" "o")
(gtk_accel_path "<Actions>//redo" "<Control>y")
(gtk_accel_path "<Actions>//state-scale" "q")
(gtk_accel_path "<Actions>//seek-prev-frame" "comma")
(gtk_accel_path "<Actions>//state-gradient" "g")
</code>
5. Save it, and run Synfig to test.
6. Enjoy!

Keyboard Shortcuts (Flash)

2009-01-07T21:10:47Z

Creek23: initial write-up

This is how you can make a Flash-like the shortcut keys of the Tools.

1. You must have Synfig installed and run at least once.
2. Find your Synfig config file under:
a.) ''Ubuntu GNU/Linux:'' /home/{username}/Synfig/
b.) ''Windows XP:'' C:\Documents and Settings\{username}\Synfig\
c.) ''Windows Vista:'' C:\Users\{username}\Synfig\
3. Open the file, named '''accelrc''', using any text editing software (GEdit, Kate, Notepad).
4. Copy the code below and paste it on the very last part of '''accelrc'''.
<code>
(gtk_accel_path "<Actions>//state-text" "t")
(gtk_accel_path "<Actions>//state-rectangle" "r")
(gtk_accel_path "<Actions>//state-rotate" "<Shift>q")
(gtk_accel_path "<Actions>//seek-next-frame" "period")
(gtk_accel_path "<Actions>//state-zoom" "z")
(gtk_accel_path "<Actions>//state-polygon" "n")
(gtk_accel_path "<Actions>//state-bline" "p")
(gtk_accel_path "<Actions>//state-normal" "v")
(gtk_accel_path "<Actions>//state-eyedrop" "i")
(gtk_accel_path "<Actions>//state-fill" "k")
(gtk_accel_path "<Actions>//state-circle" "o")
(gtk_accel_path "<Actions>//redo" "<Control>y")
(gtk_accel_path "<Actions>//state-scale" "q")
(gtk_accel_path "<Actions>//seek-prev-frame" "comma")
(gtk_accel_path "<Actions>//state-gradient" "g")
</code>
5. Save it, and run Synfig to test.
6. Enjoy!