8875974d18
Mon Feb 26 16:34:33 2001 Owen Taylor <otaylor@redhat.com> * README: Update to describe submitting patches and bug reports to bugzilla.gnome.org. Tue Feb 20 23:48:16 2001 Owen Taylor <otaylor@redhat.com> * gdk/gdkim.c,gdk/gdkprivate.h: Add private function _gdk_wcstombs_len() which takes a length. * gdk/gdkfont.c,gdk/gdkprivate.h,gdk/gdkdraw.c: Consistently handle calls to _wc() font for GDK_FONT_FONT routines by: a) for 8-bit fonts, converting to chars via wcstombs (Will make GtkLabel handle using GDK_FONT_FONT for non-iso-8859-1 a wee bit better, though GDK_FONT_FONTSET is still the only supported way to get correct i18n. #50834) b) for 16-bit fonts, assuming each wchar is a glyph index. (Broken, but no more broken than anything else)
56 lines
2.0 KiB
Plaintext
56 lines
2.0 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.13
|
|
- GNU automake 1.4
|
|
(Beta releases are at ftp://ftp.cygnus.com/pub/tromey)
|
|
- GNU libtool 1.2d
|
|
- indent (GNU indent 1.9.1 is known good)
|
|
- GNU gettext 10.35
|
|
Available in ftp://alpha.gnu.org/gnu
|
|
|
|
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 installed as well.
|
|
The installation process of glib 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
|
|
several steps to setup the tree for compilation. 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
|
|
|
|
The above commands create the "configure" script. Now you
|
|
can run the configure script in cvsroot/gtk+ to create all
|
|
the Makefiles.
|
|
|
|
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 gtk+
|
|
|
|
For information about submitting patches and commiting 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.
|
|
|
|
|