Update build/win32/vs9/README.txt

Make the VS 2008 build instructions and information
more up-to-date and clearer to people.

Please let me know if I have missed any needed details...
Thanks

diff --git a/build/win32/vs9/README.txt b/build/win32/vs9/README.txt
index 7802ab10e27243f0f2dca6d4896e6adf20f2f11b..e84424aadf63039426c87490c5dc4d1b74ca2231 100644 (file)
--- a/build/win32/vs9/README.txt
+++ b/build/win32/vs9/README.txt
@@ -6,10 +6,45 @@ first need to use some Unix-like environment or manual work to expand
 the files needed, like config.h.win32.in into config.h.win32 and the\r
 .vcprojin files here into corresponding actual .vcproj files.\r
 \r
-You will need the parts from below in the GTK+ stack: gdk-pixbuf, pango,\r
-atk and glib. External dependencies are at least zlib, libpng,\r
-proxy-libintl, fontconfig, freetype, expat.  See the corresponding\r
-README.txt file in glib for details where to unpack them.\r
+You will need the parts from below in the GTK+ stack: GDK-Pixbuf, Pango,\r
+ATK and GLib.  External dependencies are at least Cairo\r
+(with Cairo-GObject support, meaning Cairo 1.10.x or later), zlib, libpng,\r
+gettext-runtime, fontconfig*, freetype*, expat*.  See the \r
+build/win32/vs9/README.txt file in glib for details where to unpack them.\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,\r
+Cairo, ATK, Pango, GDK-Pixbuf), so that crashes caused by mixing calls\r
+to different CRTs can be kept at a minimum.  zlib, libpng, and Cairo\r
+do contain support for compiling under VS9 using VS\r
+project files and/or makefiles at this time of writing, For the\r
+GTK+ stack, VS9 project files are either available under\r
+$(srcroot)/build/vs9 in the case of GLib (stable/unstable), ATK\r
+(unstable) and GDK-Pixbuf (unstable), and should be in the next\r
+unstable version of Pango.  There is no known official VS9 build\r
+support for fontconfig (along with freetype and expat) and\r
+gettext-runtime, so please use 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
+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 GDK-Pixbuf) IJG JPEG\r
+-(optional for GDK-Pixbuf) requires zlib and IJG JPEG)libtiff\r
+-(optional for GDK-Pixbuf) jasper [jpeg-2000 library])\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\r
+-Cairo (inclusive of Cairo-GObject)\r
+-ATK\r
+-Pango\r
+-GDK-Pixbuf\r
+(note the last 3 dependencies are not interdependent, so the last 3\r
+ dependencies can be built in any order)\r
 \r
 The "install" project will copy build results and headers into their\r
 appropriate location under <root>\vs9\<PlatformName>. For instance,\r
@@ -19,5 +54,12 @@ built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into
 project files higher in the stack are supposed to look for them, not\r
 from a specific GLib source tree.\r
 \r
+*About the dependencies marked with *: I will see whether it is possible\r
+ to reduce the depepdencies on building and running GTK+ by making these\r
+ dependencies optional, as those are not compulsory components for\r
+ building and running GTK+ itself, but note that they are needed for\r
+ people running and building GIMP.  They are referred to by components\r
+ in Cairo and Pango mainly.\r
+\r
 --Tor Lillqvist <tml@iki.fi>\r
---Updated by Chun-wei Fan <fanc999 --at-- yahoo --dot-- com --dot-- tw>\r
+--Updated by Chun-wei Fan <fanc999@yahoo.com.tw>\r