Debian Codegraph @

build/win32/vs9/README.txt

raw
1 Please do not compile this package (GTK+) in paths that contain
2 spaces in them-as strange problems may occur during compilation or during
3 the use of the library.
4
5 A more detailed outline for instructions on building the GTK+ with Visual
6 C++ can be found in the following GNOME Live! page:
7
8 https://live.gnome.org/GTK%2B/Win32/MSVCCompilationOfGTKStack
9
10 This VS9 solution and the projects it includes are intented to be used
11 in a GTK+ source tree unpacked from a tarball. In a git checkout you
12 first need to use some Unix-like environment or manual work to expand
13 the files needed, like config.h.win32.in into config.h.win32 and the
14 .vcprojin files here into corresponding actual .vcproj files.
15
16 You will need the parts from below in the GTK+ stack: GDK-Pixbuf, Pango,
17 ATK and GLib. External dependencies are at least Cairo, zlib, libpng,
18 gettext-runtime; and optional dependencies are fontconfig*, freetype*
19 and expat*. See the build/win32/vs10/README.txt file in glib for
20 details where to unpack them.
21
22 It is recommended that one builds the dependencies with VS9 as far as
23 possible, especially those from and using the GTK+ stack (i.e. GLib,
24 ATK, Pango, GDK-Pixbuf), so that crashes caused by mixing calls
25 to different CRTs can be kept at a minimum. zlib, libpng, and Cairo
26 do contain support for compiling under VS9 using VS
27 project files and/or makefiles at this time of writing, For the
28 GTK+ stack, VS9 project files are either available under
29 $(srcroot)/build/vs9 in the case of GLib (stable/unstable), ATK
30 (unstable) and GDK-Pixbuf (unstable), and should be in the next
31 unstable version of Pango. There is no known official VS9 build
32 support for fontconfig (along with freetype and expat) and
33 gettext-runtime, so please use the binaries from:
34
35 ftp://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32 bit)
36 ftp://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64 bit)
37
38 The recommended build order for these dependencies:
39 (first unzip any dependent binaries downloaded from the ftp.gnome.org
40 as described in the README.txt file in the build/win32/vs9 folder)
41 -zlib
42 -libpng
43 -(optional for GDK-Pixbuf) IJG JPEG
44 -(optional for GDK-Pixbuf) requires zlib and IJG JPEG)libtiff
45 -(optional for GDK-Pixbuf) jasper [jpeg-2000 library])
46 -(optional for GLib) PCRE (version 8.12 or later, use of CMake to
47 build PCRE is recommended-see build/win32/vs9/README.txt of GLib)
48 -Cairo
49 -GLib
50 -ATK
51 -Pango
52 -GDK-Pixbuf
53 (note the last 3 dependencies are not interdependent, so the last 3
54 dependencies can be built in any order)
55
56 The "install" project will copy build results and headers into their
57 appropriate location under <root>\vs9\<PlatformName>. For instance,
58 built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into
59 <root>\vs9\<PlatformName>\lib and GTK+ headers into
60 <root>\vs9\<PlatformName>\include\gtk-2.0. This is then from where
61 project files higher in the stack are supposed to look for them, not
62 from a specific GLib source tree.
63
64 *About the dependencies marked with *: These dependencies are not
65 compulsory components for building and running GTK+ itself, but note
66 that they are needed for people running and building GIMP.
67 They are referred to by components in Cairo and Pango mainly-so decide
68 whether you will need FontConfig/FreeType support prior to building
69 Cairo and Pango, which are hard requirements for building and running
70 GTK+.
71 --Tor Lillqvist <[email protected]>
72 --Updated by Fan, Chun-wei <[email protected]>