| 1 | The Win32 port of GTK+ is a work in progress, and not as stable or |
|---|
| 2 | correct as the Unix/X11 version. For more information about the Win32 |
|---|
| 3 | port, and prebuilt runtime and developer packages see |
|---|
| 4 | http://www.gimp.org/win32/ . |
|---|
| 5 | |
|---|
| 6 | There is a gtk-1-3-win32-production branch of GTK+ that was branched |
|---|
| 7 | off from before the addition of the no-flicker and other recent |
|---|
| 8 | functionality. That is what should be used by "production" code until |
|---|
| 9 | this CVS HEAD (2.0) version is useable. (But note, the Win32 backend |
|---|
| 10 | has never been claimed to be "production quality", although it works |
|---|
| 11 | surprisingly well for the GIMP.) |
|---|
| 12 | |
|---|
| 13 | Building GTK+ on Win32 |
|---|
| 14 | ====================== |
|---|
| 15 | |
|---|
| 16 | There are two ways to build GTK+ for win32: |
|---|
| 17 | |
|---|
| 18 | 1) Use the autoconf-generated configure script, and the resulting |
|---|
| 19 | Makefiles (which use libtool and gcc to do the compilation). I use |
|---|
| 20 | this myself, but it might be hell to setup correctly. |
|---|
| 21 | |
|---|
| 22 | Personally I run configure with: |
|---|
| 23 | CC='gcc -mpentium -fnative-struct' CPPFLAGS='-I/target/include' CFLAGS=-O2 LDFLAGS='-L/target/lib' ./configure --disable-static --prefix=/target --with-gdktarget=win32 --with-wintab=/src/wtkit126 --with-ie55=/src/workshop/ie55_lib --host=i386-pc-mingw32 --enable-maintainer-mode |
|---|
| 24 | |
|---|
| 25 | It might well be that in order for this to work, you will have to get |
|---|
| 26 | a bleeding-edge version of libtool for Win32, run libtoolize yourself, |
|---|
| 27 | and then run autoconf to generate the configure script. |
|---|
| 28 | |
|---|
| 29 | 2) Use the Microsoft compiler, cl and Make, nmake. Say nmake -f |
|---|
| 30 | makefile.msc in gdk and gtk. |
|---|
| 31 | |
|---|
| 32 | Alternative 1 also generates Microsoft import libraries (.lib), if you |
|---|
| 33 | have lib.exe available. It might also work for cross-compilation from |
|---|
| 34 | Unix. |
|---|
| 35 | |
|---|
| 36 | There are hand-written makefiles for mingw (look for makefile.mingw in |
|---|
| 37 | various directories), but those haven't been kept up-to-date, and |
|---|
| 38 | probably won't work without editing. Sorry. If you make them work |
|---|
| 39 | again, by all means do submit patches. |
|---|
| 40 | |
|---|
| 41 | Note that I use method 1 myself. Hans Breuer has been taking care of |
|---|
| 42 | the MSVC makefiles. At times, we disagree a bit about various issues, |
|---|
| 43 | and the makefile.msc files might not produce identically named DLLs |
|---|
| 44 | and import libraries as the "autoconfiscated" makefiles and libtool |
|---|
| 45 | do. |
|---|
| 46 | |
|---|
| 47 | Using GTK+ on Win32 |
|---|
| 48 | =================== |
|---|
| 49 | |
|---|
| 50 | To use GTK+ on Win32, you also need either one of the above mentioned |
|---|
| 51 | compilers. Other compilers might work, but don't count on it. Look for |
|---|
| 52 | prebuilt developer packages (DLLs, import libraries, headers) on the |
|---|
| 53 | above website. |
|---|
| 54 | |
|---|
| 55 | Multi-threaded use of GTK+ on Win32 |
|---|
| 56 | =================================== |
|---|
| 57 | |
|---|
| 58 | Multi-threaded GTK+ programs might work in special simple cases, but |
|---|
| 59 | not in general. Sorry. If you have all GTK+ and GDK calls in the same |
|---|
| 60 | thread, it might work. Otherwise, probably not at all. Possible ways |
|---|
| 61 | to fix this are being investigated. |
|---|
| 62 | |
|---|
| 63 | Wintab |
|---|
| 64 | ====== |
|---|
| 65 | |
|---|
| 66 | The tablet support uses the Wintab API. The Wintab development kit can |
|---|
| 67 | be downloaded from http://www.pointing.com. Pass the --with-wintab |
|---|
| 68 | flag to configure if you use that. If you use nmake and you don't care |
|---|
| 69 | for Wintab, undefine HAVE_WINTAB in config.h.win32 and remove |
|---|
| 70 | references to the wntab32x library from the makefile before building. |
|---|
| 71 | |
|---|
| 72 | Libintl |
|---|
| 73 | ======= |
|---|
| 74 | |
|---|
| 75 | GTK wants to be built with the GNU "intl" library for |
|---|
| 76 | internationalisation (i18n). Get the version ported to Win32 (not a |
|---|
| 77 | very big deal) from the web site mentioned above. The "intl" library |
|---|
| 78 | as gets built as a DLL called libintl-1.dll. If you don't want any |
|---|
| 79 | i18n stuff, undefine ENABLE_NLS, HAVE_GETTEXT and HAVE_LIBINTL in the |
|---|
| 80 | config.h.win32 file, and remove references to the intl library from |
|---|
| 81 | the makefiles. |
|---|
| 82 | |
|---|
| 83 | ActiveIMM |
|---|
| 84 | ========= |
|---|
| 85 | |
|---|
| 86 | If you want to build a GTK+ that supports ActiveIMM (the Input Method |
|---|
| 87 | Manager for non-EastAsia locales that can be used on Win9x/NT4), you |
|---|
| 88 | need the dimm.h header file. That is somewhat difficult to find, but |
|---|
| 89 | http://msdn.microsoft.com/downloads/samples/internet/wizard/ seems to |
|---|
| 90 | be a good place to look nowadays. If you use "autoconfiscated" build, |
|---|
| 91 | pass the --with-ie55 flag to configure specifyin the location of the |
|---|
| 92 | ie55_lib directory created by downloading the IE5.5 headers and libs |
|---|
| 93 | from the above URL. |
|---|
| 94 | |
|---|
| 95 | --Tor Lillqvist <tml@iki.fi> |
|---|
