GTK is a multi-platform toolkit for creating graphical user interfaces.
Go to file
Tristan Van Berkom edd57602b8 Mass api change from GtkExtendedLayout --> GtkSizeRequest
This commit makes a few massive changes to the extended layout
code:
  a.) gtkextendedlayout.c --> gtksizerequest.c
  b.) _is_height_for_width --> get_request_mode()
  c.) get_desired_size(), get_desired_width(), get_desired_height() -->
      get_size(), get_width(), get_height()

This is the first partial commit and only effects portions
of the tree that have already been merged in master (in order to
easily cherry pick this commit).

Conflicts:

	gtk/Makefile.am
	gtk/gtk.h
	gtk/gtk.symbols
	gtk/gtkextendedlayout.h
2010-06-18 00:11:26 -04:00
build Avoid a 'EXTRA_DIST multiply defined' warning 2010-06-03 13:22:31 -04:00
contrib Install gdk-pixbuf-xlib-3.0.so.0, although this might be nuked in the near future 2010-05-10 17:15:24 +01:00
debian
demos Bug 596428 - GtkAssistant: Support ending with a progress page 2010-06-03 17:03:14 -04:00
docs [docs/gtk-faq] Close <para> tag 2010-06-17 17:43:32 +02:00
examples Convert to UTF-8 2010-05-21 20:49:41 -04:00
gdk gdk_event_get_device(): Fallback to core pointer/keyboard. 2010-06-15 21:06:11 +02:00
gdk-pixbuf Remove remaining single-include guards 2010-06-04 19:40:43 -04:00
gtk Mass api change from GtkExtendedLayout --> GtkSizeRequest 2010-06-18 00:11:26 -04:00
m4 2.19.2 2009-12-21 22:24:59 -05:00
m4macros One forgotten rename 2010-05-11 08:37:35 -04:00
modules gail: do not use removed GTK_WIDGET_*SET macros 2010-06-16 20:41:05 +02:00
perf Make 3.0 parallel-installable to 2.x 2010-05-08 01:18:53 -04:00
po Updated Spanish translation 2010-06-16 06:02:53 +02:00
po-properties Fix distcheck by removing references to gtk/gtkprogress.c 2010-06-09 09:29:50 +01:00
tests Mass api change from GtkExtendedLayout --> GtkSizeRequest 2010-06-18 00:11:26 -04:00
acinclude.m4
AUTHORS
autogen.sh Use ACLOCAL in autogen.sh 2010-05-13 17:11:12 +02:00
ChangeLog.gtk-async-file-chooser
ChangeLog.gtk-printing
ChangeLog.pre-1-0
ChangeLog.pre-1-2
ChangeLog.pre-2-0
ChangeLog.pre-2-2
ChangeLog.pre-2-4
ChangeLog.pre-2-6
ChangeLog.pre-2-8
ChangeLog.pre-2-10
ChangeLog.pre-2-12
ChangeLog.pre-2-14
ChangeLog.pre-2-16
config.h.win32.in Use a honestly bogus GTK_LOCALEDIR in config.h.win32.in 2010-04-12 13:44:59 +03:00
configure.ac Bump version 2010-06-17 21:09:50 -04:00
COPYING
gail-3.0-uninstalled.pc.in Make gail parallel-installable too 2010-05-10 20:06:10 -04:00
gail-3.0.pc.in Make gail parallel-installable too 2010-05-10 20:06:10 -04:00
gdk-3.0-uninstalled.pc.in Make 3.0 parallel-installable to 2.x 2010-05-08 01:18:53 -04:00
gdk-3.0.pc.in Make 3.0 parallel-installable to 2.x 2010-05-08 01:18:53 -04:00
gdk-pixbuf-3.0-uninstalled.pc.in Make 3.0 parallel-installable to 2.x 2010-05-08 01:18:53 -04:00
gdk-pixbuf-3.0.pc.in Make 3.0 parallel-installable to 2.x 2010-05-08 01:18:53 -04:00
git.mk
gtk-config-2.0.in
gtk-engine-check-abi.sh
gtk-zip.sh.in Some cleanups after the module cache file change 2010-05-18 19:23:06 -04:00
gtk+-3.0-uninstalled.pc.in Make 3.0 parallel-installable to 2.x 2010-05-08 01:18:53 -04:00
gtk+-3.0.pc.in Make 3.0 parallel-installable to 2.x 2010-05-08 01:18:53 -04:00
gtk+-unix-print-3.0.pc.in Make 3.0 parallel-installable to 2.x 2010-05-08 01:18:53 -04:00
gtk+.spec.in
HACKING
INSTALL.in Add notes about gobject-introspection 2010-04-03 20:59:23 -04:00
MAINTAINERS
makecopyright
Makefile.am Clean autotools configuration a bit 2010-05-13 15:54:01 +02:00
Makefile.decl
makefile.msc
NEWS Updates 2010-06-17 20:06:41 -04:00
NEWS.pre-1-0
README.commits
README.in Revert "Forward-port a GtkAdjustment compatibility fix" 2010-05-24 15:39:30 +02:00
README.win32
sanitize-la.sh Some people use a hacked libtool that doesn't even install .la files 2010-04-12 13:42:31 +03:00
sanity_check Rename configure.in to configure.ac 2010-05-07 10:07:23 +02:00

The Win32 backend in GTK+ is not as stable or correct as the X11 one.

For prebuilt runtime and developer packages see
http://ftp.gnome.org/pub/gnome/binaries/win32/

Building GTK+ on Win32
======================

First you obviously need developer packages for the compile-time
dependencies: Pango, atk, glib, gettext-runtime, libiconv, libpng,
zlib, libtiff at least. See
http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies .

After installing the dependencies, there are two ways to build GTK+
for win32.

1) GNU tools, ./configure && make install
-----------------------------------------

This requires you have mingw and MSYS.

Use the configure script, and the resulting Makefiles (which use
libtool and gcc to do the compilation). I use this myself, but it can
be hard to setup correctly.

The full script I run to build GTK+ 2.16 unpacked from a source
distribution is as below. This is from bulding GTK+ 2.16.5. I don't
use any script like this to build the development branch, as I don't
distribute any binaries from development branches.

# This is a shell script that calls functions and scripts from
# tml@iki.fi's personal work envíronment. It is not expected to be
# usable unmodified by others, and is included only for reference.

MOD=gtk+
VER=2.16.5
REV=1
ARCH=win32

THIS=${MOD}_${VER}-${REV}_${ARCH}

RUNZIP=${MOD}_${VER}-${REV}_${ARCH}.zip
DEVZIP=${MOD}-dev_${VER}-${REV}_${ARCH}.zip

HEX=`echo $THIS | md5sum | cut -d' ' -f1`
TARGET=c:/devel/target/$HEX

usedev
usemsvs6

(

set -x

DEPS=`latest --arch=${ARCH} glib atk cairo pango libpng zlib libtiff jpeg`
PROXY_LIBINTL=`latest --arch=${ARCH} proxy-libintl`

PKG_CONFIG_PATH=
for D in $DEPS; do
    PATH=/devel/dist/${ARCH}/$D/bin:$PATH
    [ -d /devel/dist/${ARCH}/$D/lib/pkgconfig ] && PKG_CONFIG_PATH=/devel/dist/${ARCH}/$D/lib/pkgconfig:$PKG_CONFIG_PATH
done

LIBPNG=`latest --arch=${ARCH} libpng`
ZLIB=`latest --arch=${ARCH} zlib`
LIBTIFF=`latest --arch=${ARCH} libtiff`
JPEG=`latest --arch=${ARCH} jpeg`

patch -p0 <<'EOF'
EOF

lt_cv_deplibs_check_method='pass_all' \
CC='gcc -mtune=pentium3 -mthreads' \
CPPFLAGS="-I/devel/dist/${ARCH}/${LIBPNG}/include \
-I/devel/dist/${ARCH}/${ZLIB}/include \
-I/devel/dist/${ARCH}/${LIBTIFF}/include \
-I/devel/dist/${ARCH}/${JPEG}/include \
-I/devel/dist/${ARCH}/${PROXY_LIBINTL}/include" \
LDFLAGS="-L/devel/dist/${ARCH}/${LIBPNG}/lib \
-L/devel/dist/${ARCH}/${ZLIB}/lib \
-L/devel/dist/${ARCH}/${LIBTIFF}/lib \
-L/devel/dist/${ARCH}/${JPEG}/lib \
-L/devel/dist/${ARCH}/${PROXY_LIBINTL}/lib -Wl,--exclude-libs=libintl.a \
-Wl,--enable-auto-image-base" \
LIBS=-lintl \
CFLAGS=-O2 \
./configure \
--with-gdktarget=win32 \
--disable-gdiplus \
--with-included-immodules \
--without-libjasper \
--enable-debug=yes \
--enable-explicit-deps=no \
--disable-gtk-doc \
--disable-static \
--prefix=$TARGET &&

libtoolcacheize &&
rm gtk/gtk.def &&
(PATH="$PWD/gdk-pixbuf/.libs:/devel/target/$HEX/bin:$PATH" make -j3 install || (rm .libtool-cache* && PATH="/devel/target/$HEX/bin:$PATH" make -j3 install)) &&

PATH="/devel/target/$HEX/bin:$PATH" gdk-pixbuf-query-loaders >/devel/target/$HEX/etc/gtk-2.0/gdk-pixbuf.loaders &&

grep -v -E 'Automatically generated|Created by|LoaderDir =' <$TARGET/etc/gtk-2.0/gdk-pixbuf.loaders >$TARGET/etc/gtk-2.0/gdk-pixbuf.loaders.temp &&
    mv $TARGET/etc/gtk-2.0/gdk-pixbuf.loaders.temp $TARGET/etc/gtk-2.0/gdk-pixbuf.loaders &&
grep -v -E 'Automatically generated|Created by|ModulesPath =' <$TARGET/etc/gtk-2.0/gtk.immodules >$TARGET/etc/gtk-2.0/gtk.immodules.temp &&
    mv $TARGET/etc/gtk-2.0/gtk.immodules.temp $TARGET/etc/gtk-2.0/gtk.immodules &&

./gtk-zip.sh &&

mv /tmp/${MOD}-${VER}.zip /tmp/$RUNZIP &&
mv /tmp/${MOD}-dev-${VER}.zip /tmp/$DEVZIP

) 2>&1 | tee /devel/src/tml/packaging/$THIS.log

(cd /devel && zip /tmp/$DEVZIP src/tml/packaging/$THIS.{sh,log}) &&
manifestify /tmp/$RUNZIP /tmp/$DEVZIP

You should not just copy the above blindly. There are some things in
the script that are very specific to *my* build setup on *my* current
machine. For instance the "latest" command, the "usedev" and
"usemsvs6" shell functions, the /devel/dist folder. The above script
is really just meant for reference, to give an idea. You really need
to understand what things like PKG_CONFIG_PATH are and set them up
properly after installing the dependencies before building GTK+.

As you see above, after running configure, one can just say "make
install", like on Unix. A post-build fix is needed, running
gdk-pixbuf-query-loaders once more to get a correct gdk-pixbuf.loaders
file.

For a 64-bit build you need to remove the gtk/gtk.def file and let it
be regenerated by the makefilery. This is because the 64-bit GTK dll
has a slightly different list of exported function names. This is on
purpose and not a bug. The API is the same at the source level, and
the same #defines of some function names to actually have a _utf8
suffix is used (just to keep the header simpler). But the
corresponding non-suffixed function to maintain ABI stability are not
needed in the 64-bit case (because there are no older EXEs around that
would require such for ABI stability).


2) Microsoft's tools
--------------------

Use the Microsoft compiler, cl and Make, nmake. Say nmake -f
makefile.msc in gdk and gtk. Be prepared to manually edit various
makefile.msc files, and the makefile snippets in build/win32.

Alternative 1 also generates Microsoft import libraries (.lib), if you
have lib.exe available. It might also work for cross-compilation from
Unix.

I use method 1 myself. Hans Breuer has been taking care of the MSVC
makefiles. At times, we disagree a bit about various issues, and for
instance the makefile.msc files might not produce identically named
DLLs and import libraries as the "autoconfiscated" makefiles and
libtool do. If this bothers you, you will have to fix the makefiles.

Using GTK+ on Win32
===================

To use GTK+ on Win32, you also need either one of the above mentioned
compilers. Other compilers might work, but don't count on it. Look for
prebuilt developer packages (DLLs, import libraries, headers) on the
above website.

Multi-threaded use of GTK+ on Win32
===================================

Multi-threaded GTK+ programs might work on Windows in special simple
cases, but not in general. Sorry. If you have all GTK+ and GDK calls
in the same thread, it might work. Otherwise, probably not at
all. Possible ways to fix this are being investigated.

Wintab
======

The tablet support uses the Wintab API. The Wintab development kit is
no longer required. The wintab.h header file is bundled with GTK+
sources. Unfortunately it seems that only Wacom tablets come with
support for the Wintab API nowadays.

--Tor Lillqvist <tml@iki.fi>, <tml@novell.com>