1 Note that all this is rather experimental.
\r
3 This VS9 solution and the projects it includes are intented to be used
\r
4 in a GTK+ source tree unpacked from a tarball. In a git checkout you
\r
5 first need to use some Unix-like environment or manual work to expand
\r
6 the files needed, like config.h.win32.in into config.h.win32 and the
\r
7 .vcprojin files here into corresponding actual .vcproj files.
\r
9 You will need the parts from below in the GTK+ stack: GDK-Pixbuf, Pango,
\r
10 ATK (2.x)** and GLib. External dependencies are at least Cairo
\r
11 (with Cairo-GObject support, meaning Cairo 1.10.x or later), zlib, libpng,
\r
12 gettext-runtime, fontconfig*, freetype*, expat*. See the
\r
13 build/win32/vs9/README.txt file in glib for details where to unpack them.
\r
15 It is recommended that one builds the dependencies with VS9 as far as
\r
16 possible, especially those from and using the GTK+ stack (i.e. GLib,
\r
17 Cairo, ATK, Pango, GDK-Pixbuf), so that crashes caused by mixing calls
\r
18 to different CRTs can be kept at a minimum. zlib, libpng, and Cairo
\r
19 do contain support for compiling under VS9 using VS
\r
20 project files and/or makefiles at this time of writing, For the
\r
21 GTK+ stack, VS9 project files are either available under
\r
22 $(srcroot)/build/vs9 in the case of GLib (stable/unstable), ATK**
\r
23 (2.x stable/unstable) and GDK-Pixbuf (unstable), and should be in the next
\r
24 unstable version of Pango. There is no known official VS9 build
\r
25 support for fontconfig (along with freetype and expat) and
\r
26 gettext-runtime, so please use the binaries from:
\r
28 ftp://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32 bit)
\r
29 ftp://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64 bit)
\r
31 The recommended build order for these dependencies:
\r
32 (first unzip any dependent binaries downloaded from the ftp.gnome.org
\r
33 as described in the README.txt file in the build/win32/vs9 folder)
\r
36 -(for GDK-Pixbuf, if not using GDI+) IJG JPEG
\r
37 -(for GDK-Pixbuf, if not using GDI+) libtiff
\r
38 [libtiff requires zlib and IJG JPEG]
\r
39 -(for GDK-Pixbuf, if not using GDI+) jasper [jpeg-2000 library])
\r
40 -(optional for GLib) PCRE (version 8.12 or later, use of CMake to
\r
41 build PCRE is recommended-see build/win32/vs9/README.txt of GLib)
\r
43 -Cairo (inclusive of Cairo-GObject)
\r
47 (note the last 3 dependencies are not interdependent, so the last 3
\r
48 dependencies can be built in any order)
\r
50 The "install" project will copy build results and headers into their
\r
51 appropriate location under <root>\vs9\<PlatformName>. For instance,
\r
52 built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into
\r
53 <root>\vs9\<PlatformName>\lib and GTK+ headers into
\r
54 <root>\vs9\<PlatformName>\include\gtk-3.0. This is then from where
\r
55 project files higher in the stack are supposed to look for them, not
\r
56 from a specific GLib source tree.
\r
58 *About the dependencies marked with *: I will see whether it is possible
\r
59 to reduce the depepdencies on building and running GTK+ by making these
\r
60 dependencies optional, as those are not compulsory components for
\r
61 building and running GTK+ itself, but note that they are needed for
\r
62 people running and building GIMP. They are referred to by components
\r
63 in Cairo and Pango mainly.
\r
65 **Regarding ATK-2.x: prior to compiling ATK-2.x, please open atkprops
\r
66 in VS under "Properties Manager" view (it is under any one of the
\r
67 build configurations, right-click on atkprops and select "Properties").
\r
68 Navigate to "User Macros", and edit the following fields:
\r
69 AtkApiVersion -> 2.0
\r
70 AtkLibToolCompatibleDllSuffix -> -2.0-0
\r
71 AtkSeperateVS9DLLSuffix -> -2-vs9
\r
72 Sorry this change did not make it upstream prior to ATK-2.0.0 release-
\r
73 this will be in the subsequent releases of ATK-2.x and was committed
\r
76 --Tor Lillqvist <tml@iki.fi>
\r
77 --Updated by Chun-wei Fan <fanc999@yahoo.com.tw>
\r
projects / ~andy / gtk / blob