Debian Codegraph @

build/win32/vs12/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 VS12 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 .vcxprojin and .vcxproj.fintersin files here into corresponding actual
15 .vcxproj and .vcxproj.filters files.
16
17 You will need the parts from below in the GTK+ stack: GDK-Pixbuf, Pango,
18 ATK and GLib. External dependencies are at least Cairo, zlib, libpng,
19 gettext-runtime; and optional dependencies are fontconfig*, freetype*
20 and expat*. See the build/win32/vs12/README.txt file in glib for
21 details where to unpack them.
22
23 It is recommended that one builds the dependencies with VS12 as far as
24 possible, especially those from and using the GTK+ stack (i.e. GLib,
25 ATK, Pango, GDK-Pixbuf), so that crashes caused by mixing calls
26 to different CRTs can be kept at a minimum. zlib, libpng, and Cairo
27 do contain support for compiling under VS12 using VS
28 project files and/or makefiles at this time of writing, For the
29 GTK+ stack, VS12 project files are either available under
30 $(srcroot)/build/vs12 in the case of GLib (stable/unstable), ATK
31 (unstable) and GDK-Pixbuf (unstable), and should be in the next
32 unstable version of Pango. There is no known official VS12 build
33 support for fontconfig (along with freetype and expat) and
34 gettext-runtime, so please use the binaries from:
35
36 ftp://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32 bit)
37 ftp://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64 bit)
38
39 The recommended build order for these dependencies:
40 (first unzip any dependent binaries downloaded from the ftp.gnome.org
41 as described in the README.txt file in the build/win32/vs12 folder)
42 -zlib
43 -libpng
44 -(optional for GDK-Pixbuf) IJG JPEG
45 -(optional for GDK-Pixbuf) requires zlib and IJG JPEG)libtiff
46 -(optional for GDK-Pixbuf) jasper [jpeg-2000 library])
47 -(optional for GLib) PCRE (version 8.12 or later, use of CMake to
48 build PCRE is recommended-see build/win32/vs12/README.txt of GLib)
49 -Cairo
50 -GLib
51 -ATK
52 -Pango
53 -GDK-Pixbuf
54 (note the last 3 dependencies are not interdependent, so the last 3
55 dependencies can be built in any order)
56
57 The "install" project will copy build results and headers into their
58 appropriate location under <root>\vs12\<PlatformName>. For instance,
59 built DLLs go into <root>\vs12\<PlatformName>\bin, built LIBs into
60 <root>\vs12\<PlatformName>\lib and GTK+ headers into
61 <root>\vs12\<PlatformName>\include\gtk-2.0. This is then from where
62 project files higher in the stack are supposed to look for them, not
63 from a specific GLib source tree.
64
65 *About the dependencies marked with *: These dependencies are not
66 compulsory components for building and running GTK+ itself, but note
67 that they are needed for people running and building GIMP.
68 They are referred to by components in Cairo and Pango mainly-so decide
69 whether you will need FontConfig/FreeType support prior to building
70 Cairo and Pango, which are hard requirements for building and running
71 GTK+.
72
73 --Tor Lillqvist <[email protected]>
74 --Updated by Fan, Chun-wei <[email protected]>