forked from AuroraMiddleware/gtk
51 lines
1.9 KiB
Plaintext
51 lines
1.9 KiB
Plaintext
If you want to hack on the Gtk+ project, it will make you life easier
|
|
to have the following packages installed:
|
|
|
|
- GNU autoconf 2.12
|
|
- GNU automake 1.2d
|
|
Available in ftp://ftp.cygnus.com/pub/tromey
|
|
- GNU libtool 1.0h
|
|
Available in ftp://alpha.gnu.org/gnu/
|
|
|
|
These should be available by ftp from prep.ai.mit.edu or any of the
|
|
fine GNU mirrors. Beta software can be found at alpha.gnu.org.
|
|
|
|
If you are accessing gtk+ via CVS, then you will need to take several
|
|
steps to get it to compile. You can do all these steps at once
|
|
by running:
|
|
|
|
cvsroot/gtk+# ./autogen.sh
|
|
|
|
Basically this does the following for you:
|
|
|
|
cvsroot/gtk+# aclocal; automake; autoconf
|
|
cvsroot/gtk+/glib# 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. You only need to call "configure" in cvsroot/gtk+
|
|
as the one in glib will be invoked automatically.
|
|
|
|
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+. You can do the following to get gtk+ from cvs:
|
|
|
|
$ export CVSROOT=':pserver:anonymous@cvs.gimp.org:/debian/home/gnomecvs'
|
|
$ cvs login
|
|
(there is no password, just hit return)
|
|
$ cvs -z9 checkout gtk+
|
|
|
|
Please submit patches to the gtk-list@redhat.com mailing list (you must
|
|
subscribe before you post, e-mail gtk-list-request@redhat.com with a
|
|
subject of "subscribe"). All kinds of contributions are accepted.
|
|
Patches that you wish to go into the distribution should also be uploaded
|
|
to ftp://ftp.gimp.org/incoming. Follow the rules there for naming your
|
|
patches.
|
|
|