Update Visual C++ README.txt

[platform/upstream/glib.git] / build / win32 / vs9 / README.txt

diff --git a/build/win32/vs9/README.txt b/build/win32/vs9/README.txt
index 86620ec..a66253e 100644 (file)
--- a/build/win32/vs9/README.txt
+++ b/build/win32/vs9/README.txt
@@ -4,26 +4,53 @@ This VS9 solution and the projects it includes are intented to be used
 in a GLib source tree unpacked from a tarball. In a git checkout you\r
 first need to use some Unix-like environment or manual work to expand\r
 the .in files needed, mainly config.h.win32.in into config.h.win32 and\r
-glibconfig.h.win32.in into glibconfig.h.win32.\r
+glibconfig.h.win32.in into glibconfig.h.win32. You will also need to\r
+expand the .vcprojin files here into .vcproj files.\r
 \r
-The only external dependency is proxy-libintl. Fetch the latest\r
-proxy-libintl-dev zipfile from\r
+The required dependencies are zlib and proxy-libintl. Fetch the latest\r
+proxy-libintl-dev and zlib-dev zipfiles from\r
 http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ for 32-bit\r
 builds, and correspondingly\r
 http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ for 64-bit\r
-builds. Set up the source tree as follows under some arbitrary top\r
+builds. \r
+\r
+One may wish to build his/her own ZLib-It is recommended that ZLib is\r
+built using the win32/Makefile.msc makefile with VS9 with the ASM routines\r
+to avoid linking problems-see win32/Makefile.msc in ZLib for more details.\r
+\r
+One may optionally use his/her own PCRE installation by selecting the\r
+(BuildType)_ExtPCRE configuration, but please note the PCRE must be built\r
+with VS9 with unicode support using the /MD (release) or /MDd (debug)\r
+runtime option which corresponds to your GLib build flavour (release, debug).\r
+(These are the defaults set by CMAKE, which is used in recent versions of PCRE.)\r
+Not doing so will most probably result in unexpected crashes in \r
+your programs due to the use of different CRTs.  If using a static PCRE\r
+build, add PCRE_STATIC to the "preprocessor definitions".\r
+Note that one may still continue to build with the bundled PCRE by selecting\r
+the (BuildType) configuration.\r
+\r
+Set up the source tree as follows under some arbitrary top\r
 folder <root>:\r
 \r
-<root>\glib\<this-glib-source-tree>\r
-<root>\glib\dependencies\<PlatformName>\proxy-libintl\r
+<root>\<this-glib-source-tree>\r
+<root>\vs9\<PlatformName>\r
 \r
 *this* file you are now reading is thus located at\r
-<root>\glib\<this-glib-source-tree>\build\win32\vs9\README.\r
+<root>\<this-glib-source-tree>\build\win32\vs9\README.\r
 \r
 <PlatformName> is either Win32 or x64, as in VS9 project files.\r
 \r
-<root>\glib\dependencies\<PlatformName>\proxy-libintl contains the\r
-unpacked proxy-libintl zip file, so that for instance libintl.h is at\r
-<root>\glib\dependencies\<PlatformName>\proxy-libintl\include\libintl.h.\r
+You should unpack the proxy-libintl-dev zip file into\r
+<root>\vs9\<PlatformName>, so that for instance libintl.h end up at\r
+<root>\vs9\<PlatformName>\include\libintl.h.\r
+\r
+The "install" project will copy build results and headers into their\r
+appropriate location under <root>\vs9\<PlatformName>. For instance,\r
+built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into\r
+<root>\vs9\<PlatformName>\lib and GLib headers into\r
+<root>\vs9\<PlatformName>\include\glib-2.0. This is then from where\r
+project files higher in the stack are supposed to look for them, not\r
+from a specific GLib source tree.\r
 \r
 --Tor Lillqvist <tml@iki.fi>\r
+--Updated by Chun-wei Fan <fanc999@gmail.com>\r