Visual C++ Builds: Update README.txt's

Update notes about usage of PCRE and for people attempting to build GLib
on a Chinese, Japanese or Korean locale.

diff --git a/build/win32/vs10/README.txt b/build/win32/vs10/README.txt
index 62ea2d9..ba58789 100644 (file)
--- a/build/win32/vs10/README.txt
+++ b/build/win32/vs10/README.txt
@@ -34,16 +34,22 @@ comes with the LibFFI source package for more details on how to build LibFFI
 on Visual C++-please note that the mozilla-build package from Mozilla is needed\r
 in order to build LibFFI on Windows.\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 VS10 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
+Please note, although using one's own existing PCRE installation to build GLib\r
+is possible, it is still recommended to build PCRE during the process of building\r
+GLib (i.e. using the Debug or Release configurations), as GLib's bundled PCRE\r
+has been patched to work optimally with GLib.  If building against an existing\r
+PCRE is desired, use the(BuildType)_ExtPCRE configurations, but one needs to ensure\r
+that the existing PCRE is:\r
+-Built with VS10\r
+-Unicode support is built in (please see the CMake options for this)\r
+-It is built with the Multithreaded DLL (/MD, for release builds) or the\r
+ Multithreaded DLL Debug (/MDd, for debug builds)\r
+\r
+If using static builds of PCRE, please add PCRE_STATIC to the "Preprocessor\r
+Definitions" of the glib project settings.\r
+\r
+Please be aware that the GLib's regex test program will only pass with PCRE directly\r
+built into GLib.\r
 \r
 Set up the source tree as follows under some arbitrary top\r
 folder <root>:\r
@@ -73,12 +79,13 @@ built DLLs go into <root>\vs10\<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
-Note: If you see C4819 warnings and you are compiling GLib on a DBCS\r
+Note: If you see C4819 errors and you are compiling GLib on a DBCS\r
 (Chinese/Korean/Japanese) version of Windows, you may need to switch\r
 to an English locale in Control Panel->Region and Languages->System->\r
 Change System Locale, reboot and rebuild to ensure GLib, Pango, GDK-Pixbuf,\r
 ATK and GTK+ is built correctly.  This is due to a bug in Visual C++ running\r
-on DBCS locales.\r
+on DBCS locales, and also affects many other opensource projects which are\r
+built with Visual C++, including but not limited to QT and the Mozilla apps.\r
 \r
 --Tor Lillqvist <tml@iki.fi>\r
 --Updated by Chun-wei Fan <fanc999@gmail.com>\r

diff --git a/build/win32/vs9/README.txt b/build/win32/vs9/README.txt
index d66dd92..158f145 100644 (file)
--- a/build/win32/vs9/README.txt
+++ b/build/win32/vs9/README.txt
@@ -34,16 +34,22 @@ comes with the LibFFI source package for more details on how to build LibFFI
 on Visual C++-please note that the mozilla-build package from Mozilla is needed\r
 in order to build LibFFI on Windows.\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
+Please note, although using one's own existing PCRE installation to build GLib\r
+is possible, it is still recommended to build PCRE during the process of building\r
+GLib (i.e. using the Debug or Release configurations), as GLib's bundled PCRE\r
+has been patched to work optimally with GLib.  If building against an existing\r
+PCRE is desired, use the(BuildType)_ExtPCRE configurations, but one needs to ensure\r
+that the existing PCRE is:\r
+-Built with VS9\r
+-Unicode support is built in (please see the CMake options for this)\r
+-It is built with the Multithreaded DLL (/MD, for release builds) or the\r
+ Multithreaded DLL Debug (/MDd, for debug builds)\r
+\r
+If using static builds of PCRE, please add PCRE_STATIC to the "Preprocessor\r
+Definitions" of the glib project settings.\r
+\r
+Please be aware that the GLib's regex test program will only pass with PCRE directly\r
+built into GLib.\r
 \r
 Set up the source tree as follows under some arbitrary top\r
 folder <root>:\r
@@ -73,12 +79,13 @@ 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
-Note: If you see C4819 warnings and you are compiling GLib on a DBCS\r
+Note: If you see C4819 errors and you are compiling GLib on a DBCS\r
 (Chinese/Korean/Japanese) version of Windows, you may need to switch\r
 to an English locale in Control Panel->Region and Languages->System->\r
 Change System Locale, reboot and rebuild to ensure GLib, Pango, GDK-Pixbuf,\r
 ATK and GTK+ is built correctly.  This is due to a bug in Visual C++ running\r
-on DBCS locales.\r
+on DBCS locales, and also affects many other opensource projects which are\r
+built with Visual C++, including but not limited to QT and the Mozilla apps.\r
 \r
 --Tor Lillqvist <tml@iki.fi>\r
 --Updated by Chun-wei Fan <fanc999@gmail.com>\r