build/win32/vs*/README.txt: Ensure line endings are consistent

We need DOS/Windows line feeds here...

2 files changed, 33 insertions, 33 deletions

diff --git a/build/win32/vs10/README.txt b/build/win32/vs10/README.txt
index f2488db0..54afd998 100644
--- a/build/win32/vs10/README.txt
+++ b/build/win32/vs10/README.txt
@@ -12,9 +12,9 @@ This VS10 solution and the projects it includes are intented to be used
 in a gobject-introspection source tree unpacked from a tarball. In a git checkout you

 first need to use some Unix-like environment, which will do the work for you.

 

-The required dependencies are Python 2.7 (2.7) or 3.3 (3.x) or later, GLib and LibFFI.
-It is recommended that GLib is built with Visual C++ 2010 to avoid problems cause by
-usage of different CRTs.
+The required dependencies are Python 2.7 (2.7) or 3.3 (3.x) or later, GLib and LibFFI.

+It is recommended that GLib is built with Visual C++ 2010 to avoid problems cause by

+usage of different CRTs.

 

 Please refer to the README.txt file in $(GLib_src_root)\build\win32\vs10 on how to build

 GLib using Visual C++ 2010

@@ -25,12 +25,12 @@ 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

 in order to build LibFFI on Windows.

 

-For Python, retrieving the official Windows binaries for 2.7 (2.x) or 3.3 (3.x) or later
-from http://www.python.org will do the job-be sure that the Python version that
-you downloaded matches the configuration of your build (win32 or x64/amd64).  Ensure that
-the correct path for your Python interpretor is set in gi-extra-paths.vsprops prior to
-opening the project files, or close the project files and delete all the *.user, *.sdf and
-*.suo files and reopening the project files.
+For Python, retrieving the official Windows binaries for 2.7 (2.x) or 3.3 (3.x) or later

+from http://www.python.org will do the job-be sure that the Python version that

+you downloaded matches the configuration of your build (win32 or x64/amd64).  Ensure that

+the correct path for your Python interpretor is set in gi-extra-paths.vsprops prior to

+opening the project files, or close the project files and delete all the *.user, *.sdf and

+*.suo files and reopening the project files.

 

 For building the Regress test project, cairo (and possibly cairo-gobject support)

 is needed.

@@ -52,15 +52,15 @@ into <root>\vs10\<PlatformName>\include\ and the compiled static libffi.lib
 <root>\vs10\<PlatformName>\lib\.

 

 The libintl.h that is used for building GLib needs to be in

-<root>\vs10\<PlatformName>\include, if not already done so.
+<root>\vs10\<PlatformName>\include, if not already done so.

 

 A working pkg-config tool is also required-it may be obtained from

 http://www.gtk.org/download/win32.php [32-bit]

 http://www.gtk.org/download/win64.php [64-bit]

 

 *** Note! ***

-Please note that due to numerous possible configurations on Python, PKG_CONFIG_PATH,
-the build of G-I is now a 2-step process: one with the Visual Studio Projects that
+Please note that due to numerous possible configurations on Python, PKG_CONFIG_PATH,

+the build of G-I is now a 2-step process: one with the Visual Studio Projects that

 will build the libraries, tools, Python Module and test DLLs (except for the everything

 test), and the other one with NMake Makefiles for building the introspection files.

 Please note that if one needs to change the installation location

@@ -72,13 +72,13 @@ variables, but the following environmental variables are needed (either by using
 or by nmake -f gi-introspection-msvc.mak xxx=yyy) for building the introspection files (which

 should be done after successfully building the Project Files):

 

-PYTHON: Full path to your Python 2.7.x/3.3.x+ interpretor (python.exe) if it is
-        not in your PATH.  Please note that only 2.7.x and 3.3.x and later works.
-        You need to use an x64/amd64 version of Python for x64 builds, and a Win32/x86
-        version of Python for Win32/x86 builds
+PYTHON: Full path to your Python 2.7.x/3.3.x+ interpretor (python.exe) if it is

+        not in your PATH.  Please note that only 2.7.x and 3.3.x and later works.

+        You need to use an x64/amd64 version of Python for x64 builds, and a Win32/x86

+        version of Python for Win32/x86 builds

 PKG_CONFIG_PATH: Location of the .pc (pkg-config) files, especially for the GLib .pc files.

 

-Please see $(srcroot)\build\win32\gi-introspection-msvc.mak for more details.  Doing
+Please see $(srcroot)\build\win32\gi-introspection-msvc.mak for more details.  Doing

 "nmake -f gi-introspection-msvc.mak (options omitted)" will build the various introspection files,

 and "nmake -f gi-introspection-msvc.mak (options omitted) install-introspection" will copy the introspection

 files to <root>\vs10\<PlatformName>\share\gir-1.0 (.gir files) and

diff --git a/build/win32/vs9/README.txt b/build/win32/vs9/README.txt
index 85e17a8d..2911fc17 100644
--- a/build/win32/vs9/README.txt
+++ b/build/win32/vs9/README.txt
@@ -12,9 +12,9 @@ This VS9 solution and the projects it includes are intented to be used
 in a gobject-introspection source tree unpacked from a tarball. In a git checkout you

 first need to use some Unix-like environment, which will do the work for you.

 

-The required dependencies are Python 2.7 (2.7) or 3.3 (3.x) or later, GLib and LibFFI.
-It is recommended that GLib is built with Visual C++ 2008 to avoid problems cause by
-usage of different CRTs.
+The required dependencies are Python 2.7 (2.7) or 3.3 (3.x) or later, GLib and LibFFI.

+It is recommended that GLib is built with Visual C++ 2008 to avoid problems cause by

+usage of different CRTs.

 

 Please refer to the README.txt file in $(GLib_src_root)\build\win32\vs9 on how to build

 GLib using Visual C++ 2008

@@ -25,12 +25,12 @@ 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

 in order to build LibFFI on Windows.

 

-For Python, retrieving the official Windows binaries for 2.7 (2.x) or 3.3 (3.x) or later
-from http://www.python.org will do the job-be sure that the Python version that
-you downloaded matches the configuration of your build (win32 or x64/amd64).  Ensure that
-the correct path for your Python interpretor is set in gi-extra-paths.vsprops prior to
-opening the project files, or close the project files and delete all the *.user, *.ncb and
-*.suo files and reopening the project files.
+For Python, retrieving the official Windows binaries for 2.7 (2.x) or 3.3 (3.x) or later

+from http://www.python.org will do the job-be sure that the Python version that

+you downloaded matches the configuration of your build (win32 or x64/amd64).  Ensure that

+the correct path for your Python interpretor is set in gi-extra-paths.vsprops prior to

+opening the project files, or close the project files and delete all the *.user, *.ncb and

+*.suo files and reopening the project files.

 

 For building the Regress test project, cairo (and possibly cairo-gobject support)

 is needed.

@@ -59,8 +59,8 @@ http://www.gtk.org/download/win32.php [32-bit]
 http://www.gtk.org/download/win64.php [64-bit]

 

 *** Note! ***

-Please note that due to numerous possible configurations on Python and PKG_CONFIG_PATH,
-the build of G-I is now a 2-step process: one with the Visual Studio Projects that
+Please note that due to numerous possible configurations on Python and PKG_CONFIG_PATH,

+the build of G-I is now a 2-step process: one with the Visual Studio Projects that

 will build the libraries, tools, Python Module and test DLLs (except for the everything

 test), and the other one with NMake Makefiles for building the introspection files.

 Please note that if one needs to change the installation location

@@ -72,13 +72,13 @@ variables, but the following environmental variables are needed (either by using
 or by nmake -f gi-introspection-msvc.mak xxx=yyy) for building the introspection files (which

 should be done after successfully building the Project Files):

 

-PYTHON: Full path to your Python 2.7.x/3.3.x+ interpretor (python.exe) if it is
-        not in your PATH.  Please note that only 2.7.x and 3.3.x and later works.
-        You need to use an x64/amd64 version of Python for x64 builds, and a Win32/x86
-        version of Python for Win32/x86 builds
+PYTHON: Full path to your Python 2.7.x/3.3.x+ interpretor (python.exe) if it is

+        not in your PATH.  Please note that only 2.7.x and 3.3.x and later works.

+        You need to use an x64/amd64 version of Python for x64 builds, and a Win32/x86

+        version of Python for Win32/x86 builds

 PKG_CONFIG_PATH: Location of the .pc (pkg-config) files, especially for the GLib .pc files.

 

-Please see $(srcroot)\build\win32\gi-introspection-msvc.mak for more details.  Doing
+Please see $(srcroot)\build\win32\gi-introspection-msvc.mak for more details.  Doing

 "nmake -f gi-introspection-msvc.mak (options omitted)" will build the various introspection files,

 and "nmake -f gi-introspection-msvc.mak (options omitted) install-introspection" will copy the introspection

 files to <root>\vs9\<PlatformName>\share\gir-1.0 (.gir files) and <root>\vs9\<PlatformName>\lib\girepository-1.0