summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorCody Russell <bratsche@gnome.org>2007-08-17 15:50:10 +0000
committerCody Russell <bratsche@src.gnome.org>2007-08-17 15:50:10 +0000
commit2001b61a5521e624751dcb24d391abbd848edef0 (patch)
tree3678af4d94c51e2b8120e718a39c57b7d2a6f0da /HACKING
parentfda0eb309b33b2bf078caa33d92c89fcf7cdc880 (diff)
downloadgtk+-2001b61a5521e624751dcb24d391abbd848edef0.tar.gz
HACKING Updated documentation about SVN, and updated dependency
2007-08-17 Cody Russell <bratsche@gnome.org> * HACKING * README.cvs-commits: Updated documentation about SVN, and updated dependency information. (#447883, Yesudeep Mangalapilly) svn path=/trunk/; revision=18644
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING68
1 files changed, 36 insertions, 32 deletions
diff --git a/HACKING b/HACKING
index 53ccc8f72c..bd8cfc8e7a 100644
--- a/HACKING
+++ b/HACKING
@@ -1,55 +1,59 @@
If you want to hack on the GTK+ project, you'll need to have
the following packages installed:
- - GNU autoconf 2.52
- - GNU automake 1.4
- - GNU libtool 1.4
- - indent (GNU indent 1.9.1 is known good)
- - GNU gettext 10.40
+ - 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.
-In order to get CVS gtk+ installed on your system, you need to have
-the most recent CVS version of glib, pango, and atk installed as well.
+Up-to-date instructions about developing GNOME applications and libraries
+can be found here:
+
+ http://developer.gnome.org
+
+including information about using Subversion with GNOME:
+
+ http://developer.gnome.org/tools/svn.html
+
+In order to get SVN gtk+ installed on your system, you need to have
+the most recent SVN 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+.
-To compile a CVS version of gtk+ on your system, you will need to take
+If at all possible, please use SVN to get the latest development version of
+gtk+ and glib. You can do the following to get glib and gtk+ from SVN:
+
+ $ svn checkout http://svn.gnome.org/svn/glib/trunk glib
+ $ svn checkout http://svn.gnome.org/svn/pango/trunk pango
+ $ svn checkout http://svn.gnome.org/svn/atk/trunk atk
+ $ svn checkout http://svn.gnome.org/svn/gtk+/trunk gtk+
+
+To compile the SVN 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:
- cvsroot/gtk+# ./autogen.sh
+ gtk+$ ./autogen.sh
Basically this does the following for you:
- cvsroot/gtk+# aclocal; automake; autoconf
+ gtk+$ aclocal; automake; autoconf
- The above commands create the "configure" script. Now you
- can run the configure script in cvsroot/gtk+ to create all
- the Makefiles.
+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
+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.
-
-If at all possible, please use CVS to get the latest development version of
-gtk+ and glib. You can do the following to get glib and gtk+ from cvs:
-
- $ export CVSROOT=':pserver:anonymous@cvs.gnome.org:/cvs/gnome'
- $ cvs login
- (there is no password, just hit return)
- $ cvs -z3 checkout glib
- $ cvs -z3 checkout pango
- $ cvs -z3 checkout atk
- $ cvs -z3 checkout gtk+
+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 committing changes
-to CVS, see the README and README.cvs-commits files. In particular,
-don't, under any circumstances, commit anything to CVS before
-reading and understanding README.cvs-commmits.
-
-
+to SVN, see the `README' and `README.cvs-commits' files. In particular,
+don't, under any circumstances, commit anything to SVN before
+reading and understanding `README.cvs-commmits'.