Building with Visual Studio\r
===========================\r
\r
-In an unpacked tarball, you will find in build\win32\vs9 a solution\r
-file that can be used to build the GLib DLLs and some auxiliary\r
-programs. Read the README.txt file in that folder for more\r
-information. Note that you will need a libintl implementation, and\r
-zlib.\r
+Please do not build GLib in paths that contain spaces in them, as\r
+this may cause problems during compilation and during usage of the\r
+library.\r
+\r
+In an unpacked tarball, you will find in build\win32\vs9 (VS 2008) and\r
+build\win32\vs10 (VS 2010) a solution file that can be used to build\r
+the GLib DLLs and some auxiliary programs under VS 2008 and VS 2010\r
+(Express Edition will suffice with the needed dependencies) respectively.\r
+Read the README.txt file in those folders for more\r
+information. Note that you will need a libintl implementation, zlib, and \r
+libFFI.\r
\r
If you are building from a GIT checkout, you will first need to use some\r
Unix-like environment or run build/win32/setup.py, \r
-Note that all this is rather experimental.\r
+Please do not compile this package (GLib) in paths that contain\r
+spaces in them-as strange problems may occur during compilation or during\r
+the use of the library.\r
\r
This VS10 solution and the projects it includes are intented to be used\r
in a GLib source tree unpacked from a tarball. In a git checkout you\r
-Note that all this is rather experimental.\r
+Please do not compile this package (GLib) in paths that contain\r
+spaces in them-as strange problems may occur during compilation or during\r
+the use of the library.\r
\r
This VS9 solution and the projects it includes are intented to be used\r
in a GLib source tree unpacked from a tarball. In a git checkout you\r