HACKING - gtk in GSettings-GTK+

If you want to hack on the GTK+ project, you'll need to have
the following packages installed:

        - GNU autoconf 2.54
        - GNU automake 1.7
        - GNU libtool 1.4
        - indent (GNU indent 1.9.1 is known good)
        - GNU gettext 10.40

These should be available by ftp from ftp.gnu.org or any of the
fine GNU mirrors.  Beta software can be found at alpha.gnu.org.

Up-to-date instructions about developing GNOME applications and libraries
can be found here:

        http://developer.gnome.org

Information about using git with GNOME can be found here:

        http://live.gnome.org/Git

In order to get GIT gtk+ installed on your system, you need to have
the most recent GIT versions of glib, pango, and atk installed as well.
The installation process of these libraries is similar to that of gtk+, but
needs to be fulfilled prior to installation of gtk+.

If at all possible, please use GIT to get the latest development version of
gtk+ and glib. You can do the following to get glib and gtk+ from GIT:

        $ git clone git://git.gnome.org/glib
        $ git clone git://git.gnome.org/pango
        $ git clone git://git.gnome.org/atk
        $ git clone git://git.gnome.org/gtk+

Note: if you plan to push changes to back to the master repository and
have a gnome account, you want to use the following instead:

        $ git clone ssh://<username>@git.gnome.org/git/gtk+

To compile the GIT version of gtk+ on your system, you will need to take
several steps to setup the tree for compilation.  You can do all these
steps at once by running:

        gtk+$ ./autogen.sh

Basically this does the following for you:

        gtk+$ aclocal; automake; autoconf

The above commands create the `configure' script.  Now you
run the `configure' script in `gtk+/' to create all Makefiles.
More information about that in `INSTALL'.

Before running `autogen.sh' or `configure', make sure you have libtool
in your path.

Note that autogen.sh runs configure for you.  If you wish to pass
options like `--prefix=/usr' to `configure' you can give those options
to `autogen.sh' and they will be passed on to `configure'.

For information about submitting patches and pushing changes
to GIT, see the `README' and `README.commits' files. In particular,
don't, under any circumstances, push anything to GIT before
reading and understanding `README.commmits'.

1	If you want to hack on the GTK+ project, you'll need to have
2	the following packages installed:
3
4	- GNU autoconf 2.54
5	- GNU automake 1.7
6	- GNU libtool 1.4
7	- indent (GNU indent 1.9.1 is known good)
8	- GNU gettext 10.40
9
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.
12
13	Up-to-date instructions about developing GNOME applications and libraries
14	can be found here:
15
16	http://developer.gnome.org
17
18	Information about using git with GNOME can be found here:
19
20	http://live.gnome.org/Git
21
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+.
26
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:
29
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+
34
35	Note: if you plan to push changes to back to the master repository and
36	have a gnome account, you want to use the following instead:
37
38	$ git clone ssh://<username>@git.gnome.org/git/gtk+
39
40	To compile the GIT version of gtk+ on your system, you will need to take
41	several steps to setup the tree for compilation. You can do all these
42	steps at once by running:
43
44	gtk+$ ./autogen.sh
45
46	Basically this does the following for you:
47
48	gtk+$ aclocal; automake; autoconf
49
50	The above commands create the `configure' script. Now you
51	run the `configure' script in `gtk+/' to create all Makefiles.
52	More information about that in `INSTALL'.
53
54	Before running `autogen.sh' or `configure', make sure you have libtool
55	in your path.
56
57	Note that autogen.sh runs configure for you. If you wish to pass
58	options like `--prefix=/usr' to `configure' you can give those options
59	to `autogen.sh' and they will be passed on to `configure'.
60
61	For information about submitting patches and pushing changes
62	to GIT, see the `README' and `README.commits' files. In particular,
63	don't, under any circumstances, push anything to GIT before
64	reading and understanding `README.commmits'.

Gitorious