Update Windows READMEs

-Tell people about that libFFI is now needed.
-Tell people not to compile GLib in paths containing spaces.

README.win32

@@ -159,11 +159,17 @@ and libtool documentation.
 Building with Visual Studio
 ===========================
 
-In an unpacked tarball, you will find in build\win32\vs9 a solution
-file that can be used to build the GLib DLLs and some auxiliary
-programs. Read the README.txt file in that folder for more
-information. Note that you will need a libintl implementation, and
-zlib.
+Please do not build GLib in paths that contain spaces in them, as
+this may cause problems during compilation and during usage of the
+library.
+
+In an unpacked tarball, you will find in build\win32\vs9 (VS 2008) and
+build\win32\vs10 (VS 2010) a solution file that can be used to build
+the GLib DLLs and some auxiliary programs under VS 2008 and VS 2010
+(Express Edition will suffice with the needed dependencies) respectively.
+Read the README.txt file in those folders for more
+information. Note that you will need a libintl implementation, zlib, and 
+libFFI.
 
 If you are building from a GIT checkout, you will first need to use some
 Unix-like environment or run build/win32/setup.py, 

build/win32/vs10/README.txt

@@ -1,4 +1,6 @@
-Note that all this is rather experimental.
+Please do not compile this package (GLib) in paths that contain
+spaces in them-as strange problems may occur during compilation or during
+the use of the library.
 
 This VS10 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

build/win32/vs9/README.txt

@@ -1,4 +1,6 @@
-Note that all this is rather experimental.
+Please do not compile this package (GLib) in paths that contain
+spaces in them-as strange problems may occur during compilation or during
+the use of the library.
 
 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