[swfmill] building svn version

[Ralf Fuest]

Hello Mark,
you don't need to copy Makefile.in from a pre-release, this can cause
problems when Makefile.am is changed. The build system requires a
ChangeLog file to work correctly, it should be added to SVN to make
compiling easier. Also running ./configure isn't necessary, because it's
run by ./autogen.sh. My SVG patch also includes a changed version of
autogen.sh that allows you to specify the configure parameters when
calling autogen.sh (e.g. ./autogen.sh --prefix=/usr).

Here is an updated version of the build instructions:

$ mkdir swfmill
$ cd swfmill
$ svn co http://swfmill.org/svn/trunk
$ cd trunk
$ mv ~/Desktop/svg.patch.bz2 .
$ bunzip2 -d svg.patch.bz2
$ patch -p0 < svg.patch
$ touch ChangeLog
$ ./autogen.sh
$ make
$ su
# make install

Ralf

> Below is what I have to do, on Gentoo. That means I don't have to deal
> with dependencies, because it's close to impossible to have a working
> system without having everything swfmill needs already... lucky me. :)
> What you do need, apart from the dependencies, is (of course) Ralf's
> patch and Makefile.in (I took the one out of the latest pre-release).
> I assume both are on the desktop, just adjust the paths if you have
> them somewhere else.
> 
> $ mkdir swfmill
> $ cd swfmill
> $ svn co http://swfmill.org/svn/trunk
> $ cd trunk
> $ mv ~/Desktop/svg.patch.bz2 .
> $ bunzip2 -d svg.patch.bz2
> $ patch -p0 < svg.patch
> $ mv  ~/Desktop/Makefile.in .
> $ ./autogen.sh
> $ ./configure
> $ make
> $ su
> # make install
> 
> So, that's what works for me -- your mileage may vary. If somebody
> succeeds in building a statically linked mac/win binary, why not
> upload it somewhere so the others can play, too?
> 
> HTH,
> Mark