From 26e8f0e5f0744fc56829a40aadf1c5eedc98bd3f Mon Sep 17 00:00:00 2001 From: Chun-wei Fan Date: Wed, 18 May 2011 11:43:42 +0800 Subject: Update Visual C++ 2008 README.txt Make the instructions to compile Pango with Visual C++ clearer. --- build/win32/vs9/README.txt | 57 ++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 55 insertions(+), 2 deletions(-) (limited to 'build') diff --git a/build/win32/vs9/README.txt b/build/win32/vs9/README.txt index b7c4e908..62252229 100644 --- a/build/win32/vs9/README.txt +++ b/build/win32/vs9/README.txt @@ -6,14 +6,66 @@ 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 : -\pango\ +\ \vs9\ +Unzip the binaries obtained from ftp.gnome.org in \vs9\, +and build the following, if not already done so: + +Note: put the resulting zlib, libpng, pcre and Cairo files as follows: + .dll files: \vs9\\bin + .lib files: \vs9\\lib + .h files: \vs9\\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 \, 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 -\pango\\build\win32\vs9\README.txt. +\\build\win32\vs9\README.txt. is either Win32 or x64, as in VS9 project files. @@ -33,3 +85,4 @@ headers are present, and an "install tree" where only public headers are present. --Tor Lillqvist +--Updated by Fan, Chun-wei -- cgit v1.2.1