1 If you want to hack on the Gtk+ project, it will make you life easier
2 to have the following packages installed:
6 (Beta releases are at ftp://ftp.cygnus.com/pub/tromey)
9 These should be available by ftp from ftp.gnu.org or any of the
10 fine GNU mirrors. Beta software can be found at alpha.gnu.org.
12 In order to get CVS gtk+ installed on your system, you need to have
13 the most recent CVS version of glib installed as well.
14 The installation process of glib is similar to that of gtk+, but
15 needs to be fulfilled prior to installation of gtk+.
17 To compile a CVS version of gtk+ on your system, you will need to take
18 several steps to setup the tree for compilation. You can do all these
19 steps at once by running:
21 cvsroot/gtk+# ./autogen.sh
23 Basically this does the following for you:
25 cvsroot/gtk+# aclocal; automake; autoconf
27 The above commands create the "configure" script. Now you
28 can run the configure script in cvsroot/gtk+ to create all
31 Before running autogen.sh or configure, make sure you have libtool
34 Note that autogen.sh runs configure for you. If you wish to pass
35 options like --prefix=/usr to configure you can give those options
36 to autogen.sh and they will be passed on to configure.
38 If at all possible, please use CVS to get the latest development version of
39 gtk+ and glib. You can do the following to get glib and gtk+ from cvs:
41 $ export CVSROOT=':pserver:anonymous@cvs.gimp.org:/debian/home/gnomecvs'
43 (there is no password, just hit return)
44 $ cvs -z9 checkout glib
45 $ cvs -z9 checkout gtk+
47 Please submit patches to the gtk-list@redhat.com mailing list (you must
48 subscribe before you post, e-mail gtk-list-request@redhat.com with a
49 subject of "subscribe"). All kinds of contributions are accepted.
50 Patches that you wish to go into the distribution should also be uploaded
51 to ftp://ftp.gimp.org/incoming. Follow the rules there for naming your