1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
|
Note that all this is rather experimental.
Please do not compile Pango in a path with spaces to avoid potential
problems during the build and/or during the usage of the Pango
library.
This VS9 solution and the projects it includes are intented to be used
in a Pango source tree unpacked from a tarball. In a git checkout you
first need to use some Unix-like environment or manual work to expand
files as needed, for instance the .vcprojin files here into .vcproj
files.
It is recommended that GLib is compiled with VS9 to compile Pango.
External dependencies are at least Cairo, zlib, libpng,
gettext-runtime; optional dependencies include fontconfig, freetype,
and expat. Please see the build\win32\vs9\README.txt file in glib
for details where to unpack them.
Decide first whether you would want to use fontconfig (which also includes
freetype) prior to starting this build-Cairo needs to be built with freetype
*and* fontconfig support before building Pango. You will need fontconfig
support if you plan on building GIMP, or if you need support for complex
language scripts via fontconfig.
It is recommended that one builds the dependencies with VS9 as far as
possible, especially those from and using the GTK+ stack (i.e. GLib and
Cairo, [Cairo if one is planning to use GTK+ 3.x]), so that crashes
caused by mixing calls to different CRTs can be kept at a minimum.
zlib, libpng, and Cairo do contain support for compiling under VS9
using VS project files and/or makefiles at this time of writing.
For GLib, VS9 project files are available under
$(srcroot)\build\vs9 in the case of GLib (stable/unstable).
There is no known official VS9 build support for fontconfig
(along with freetype and expat which will work with the pre-compiled
fontconfig binary on ftp.gnome.org) and gettext-runtime, so please use
the binaries from:
ftp://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32 bit)
ftp://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64 bit)
Set up the source tree as follows under some arbitrary top folder
<root>:
<root>\<this-pango-source-tree>
<root>\vs9\<PlatformName>
Unzip the binaries obtained from ftp.gnome.org in <root>\vs9\<PlatformName>,
and build the following, if not already done so:
Note: put the resulting zlib, libpng, pcre and Cairo files as follows:
.dll files: <root>\vs9\<PlatformName>\bin
.lib files: <root>\vs9\<PlatformName>\lib
.h files: <root>\vs9\<PlatformName>\include
The recommended build order for these dependencies:
(first unzip any dependent binaries downloaded from the ftp.gnome.org
as described in the README.txt file in the build\win32\vs9 folder)
-zlib
-libpng
-(optional for GLib) PCRE (version 8.12 or later, use of CMake to
build PCRE is recommended-see build\win32\vs9\README.txt of GLib)
-GLib (put the sources in <root>\<GLib-Source-Tree>, and build it from
there with VS9)
-Cairo (inclusive of Cairo-GObject-if using GTK+-3.x)
Use the pango_fc.sln solution if usage of fontconfig is desired; otherwise
use the pango.sln solution.
*this* file you are now reading is thus located at
<root>\<this-pango-source-tree>\build\win32\vs9\README.txt.
<PlatformName> is either Win32 or x64, as in VS9 project files.
You should unpack the glib-dev zip file into
<root>\vs9\<PlatformName>, so that for instance glib.h ends up at
<root>\vs9\<PlatformName>\include\glib-2.0\glib.h.
The "install" project will copy build results and headers into their
appropriate location under <root>\vs9\<PlatformName>. For instance,
built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into
<root>\vs9\<PlatformName>\lib and headers into
<root>\vs9\<PlatformName>\include\pangpo-1.0. This is then from where
project files higher in the stack are supposed to look for them, not
from a specific Pango source tree like this one. It is important to
keep separate the concept of a "source tree", where also non-public
headers are present, and an "install tree" where only public headers
are present.
--Tor Lillqvist <tml@iki.fi>
--Updated by Fan, Chun-wei <fanc999@yahoo.com.tw>
|
