2 Building Gnash from its git repository
4 The source code of Gnash is checked into a git repository. (See the main
5 web page for Gnash for the current details on where that repository is.)
6 The instructions for building Gnash in README and INSTALL assume that
7 you are starting from a released "tarball" (e.g. gnash-VERSION.tar.gz).
8 The tarball contains some files that are not in the original source code
9 in git. They are generated using tools that not everyone is expected
10 to have. This simplifies the process of building Gnash releases, for
13 People who are actively working on maintaining Gnash need to have these
14 extra tools. They are used to build configuration files, international
15 message translation catalogs, and such. After you check out the source
16 code of Gnash from git, you'll have to run a single script that rebuilds
17 all these files. This script is called "./autogen.sh", and it lives
18 in the top-level directory of gnash. You run it without any arguments.
19 When it finishes, you can run "./configure", with or without arguments,
20 as instructed in the README and INSTALL files.
22 A variety of GNU programs are required when checking out the
23 git tree and building the auto-generated files. If anything is
24 missing, ./autogen.sh will (probably) tell you, or produce a relatively
25 understandable error message. When in doubt, look at the *first*
26 error message. Here are the programs required:
28 GNU Minimum RPM or DEB package names:
29 Package Version Debian Ubuntu Fedora
30 ------- ------- ----------- ------------ ---------
31 automake 1.9.6 automake1.9 automake1.9 automake
32 autoconf 2.59 autoconf autoconf
34 gettext 0.14.6 gettext gettext
35 libtool 1.5.22 libtool libtool
36 1.5.22 libltdl3-dev libtool
38 The "Minimum Version" is not necessarily the lowest version that will work;
39 it's the lowest version that the Gnash team has recently tested with.
40 (You'll also need some very common tools, for example the standard Unix/GNU
41 core utilities (ls, mv); text utilities (grep, sed), and shell (sh).
42 Unless your system is very unusual, these will already be installed.)
44 The version dependencies among these tools are, unfortunately, more
45 complicated than we can describe here. When ./autogen.sh is failing
46 for you, either upgrade all the things in the above table to the latest
47 version available (which may break other packages you're trying to build),
48 or seek a compatible set of tools, perhaps the set that comes by default
49 in your operating system (if any).
51 If you are unable to run ./autogen.sh successfully on your system, consider
52 building Gnash from a tarball release. Or, move the git tree to a system
53 on which you can run ./autogen.sh successfully, then move it back to the
54 system you are trying to build on.
56 Once ./autogen.sh completes successfully, you can go on with the normal
57 instructions found in the README file.