1 If you want to hack on the GTK+ project, you'll need to have
2 the following packages installed:
7 - indent (GNU indent 1.9.1 is known good)
10 These should be available by ftp from ftp.gnu.org or any of the
11 fine GNU mirrors. Beta software can be found at alpha.gnu.org.
13 Up-to-date instructions about developing GNOME applications and libraries
16 http://developer.gnome.org
18 Information about using git with GNOME can be found here:
20 http://live.gnome.org/GitMigration
22 In order to get GIT gtk+ installed on your system, you need to have
23 the most recent GIT versions of glib, pango, and atk installed as well.
24 The installation process of these libraries is similar to that of gtk+, but
25 needs to be fulfilled prior to installation of gtk+.
27 If at all possible, please use GIT to get the latest development version of
28 gtk+ and glib. You can do the following to get glib and gtk+ from GIT:
30 $ git clone git://git.gnome.org/glib
31 $ git clone git://git.gnome.org/pango
32 $ git clone git://git.gnome.org/atk
33 $ git clone git://git.gnome.org/gtk+
35 To compile the GIT version of gtk+ on your system, you will need to take
36 several steps to setup the tree for compilation. You can do all these
37 steps at once by running:
41 Basically this does the following for you:
43 gtk+$ aclocal; automake; autoconf
45 The above commands create the `configure' script. Now you
46 run the `configure' script in `gtk+/' to create all Makefiles.
47 More information about that in `INSTALL'.
49 Before running `autogen.sh' or `configure', make sure you have libtool
52 Note that autogen.sh runs configure for you. If you wish to pass
53 options like `--prefix=/usr' to `configure' you can give those options
54 to `autogen.sh' and they will be passed on to `configure'.
56 For information about submitting patches and pushing changes
57 to GIT, see the `README' and `README.commits' files. In particular,
58 don't, under any circumstances, push anything to GIT before
59 reading and understanding `README.commmits'.