Update Visual C++ 2008 README.txt

Make the instructions to compile Pango with Visual C++
clearer.

diff --git a/build/win32/vs9/README.txt b/build/win32/vs9/README.txt
index b7c4e90..6225222 100644 (file)
--- 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\r
 files.\r
 \r
+\r
+It is recommended that GLib is compiled with VS9 to compile Pango.\r
+External dependencies are at least Cairo,  zlib, libpng,\r
+gettext-runtime; optional dependencies include fontconfig, freetype,\r
+and expat.  Please see the build/win32/vs9/README.txt file in glib\r
+for details where to unpack them.\r
+\r
+Decide first whether you would want to use fontconfig (which also includes\r
+freetype) prior to starting this build-Cairo needs to be built with freetype\r
+*and* fontconfig support before building Pango.  You will need fontconfig\r
+support if you plan on building GIMP, or if you need support for complex\r
+language scripts via fontconfig.\r
+\r
+It is recommended that one builds the dependencies with VS9 as far as\r
+possible, especially those from and using the GTK+ stack (i.e. GLib and\r
+Cairo, [Cairo if one is planning to use GTK+ 3.x]), so that crashes\r
+caused by mixing calls to different CRTs can be kept at a minimum.\r
+zlib, libpng, and Cairo do contain support for compiling under VS9\r
+using VS project files and/or makefiles at this time of writing.\r
+For GLib, VS9 project files are available under\r
+$(srcroot)/build/vs9 in the case of GLib (stable/unstable).\r
+\r
+There is no known official VS9 build support for fontconfig\r
+(along with freetype and expat which will work with the pre-compiled\r
+fontconfig binary on ftp.gnome.org) and gettext-runtime, so please use\r
+the binaries from:\r
+\r
+ftp://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32 bit)\r
+ftp://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64 bit)\r
+\r
 Set up the source tree as follows under some arbitrary top folder\r
 <root>:\r
 \r
-<root>\pango\<this-pango-source-tree>\r
+<root>\<this-pango-source-tree>\r
 <root>\vs9\<PlatformName>\r
 \r
+Unzip the binaries obtained from ftp.gnome.org in <root>\vs9\<PlatformName>,\r
+and build the following, if not already done so: \r
+\r
+Note: put the resulting zlib, libpng, pcre and Cairo files as follows:\r
+ .dll files: <root>\vs9\<PlatformName>\bin\r
+ .lib files: <root>\vs9\<PlatformName>\lib\r
+ .h files: <root>\vs9\<PlatformName>\include\r
+\r
+The recommended build order for these dependencies:\r
+(first unzip any dependent binaries downloaded from the ftp.gnome.org\r
+ as described in the README.txt file in the build/win32/vs9 folder)\r
+-zlib\r
+-libpng\r
+-(optional for GLib) PCRE (version 8.12 or later, use of CMake to\r
+  build PCRE is recommended-see build/win32/vs9/README.txt of GLib)\r
+-GLib (put the sources in <root>\<GLib-Source-Tree>, and build it from\r
+       there with VS9)\r
+-Cairo (inclusive of Cairo-GObject-if using GTK+-3.x)\r
+\r
+Use the pango_fc.sln solution if usage of fontconfig is desired; otherwise\r
+use the pango.sln solution.\r
+\r
 *this* file you are now reading is thus located at\r
-<root>\pango\<this-pango-source-tree>\build\win32\vs9\README.txt.\r
+<root>\<this-pango-source-tree>\build\win32\vs9\README.txt.\r
 \r
 <PlatformName> is either Win32 or x64, as in VS9 project files.\r
 \r
@@ -33,3 +85,4 @@ headers are present, and an "install tree" where only public headers
 are present.\r
 \r
 --Tor Lillqvist <tml@iki.fi>\r
+--Updated by Fan, Chun-wei <fanc999@yahoo.com.tw>\r