Update VS2010 READNE.txt

This file should have Windows CRLF EOL as well

1 files changed, 90 insertions, 90 deletions

diff --git a/build/win32/vs10/README.txt b/build/win32/vs10/README.txt
index a31fca06f2..0fb5cb6a03 100644
--- a/build/win32/vs10/README.txt
+++ b/build/win32/vs10/README.txt
@@ -1,90 +1,90 @@
-Note that all this is rather experimental.
-
-This VS10 solution and the projects it includes are intented to be used
-in a GTK+ source tree unpacked from a tarball. In a git checkout you
-first need to use some Unix-like environment or manual work to expand
-the files needed, like config.h.win32.in into config.h.win32 and the
-.vcprojin files here into corresponding actual .vcproj files.
-
-You will need the parts from below in the GTK+ stack: GDK-Pixbuf, Pango,
-ATK and GLib.  External dependencies are at least Cairo
-(with Cairo-GObject support, meaning Cairo 1.10.x or later), zlib, libpng,
-gettext-runtime, fontconfig*, freetype*, expat*.  See the 
-build/win32/vs10/README.txt file in glib for details where to unpack them.
-
-It is recommended that one builds the dependencies with VS10 as far as
-possible, especially those from and using the GTK+ stack (i.e. GLib,
-Cairo, ATK, Pango, GDK-Pixbuf), so that crashes caused by mixing calls
-to different CRTs can be kept at a minimum.
-
-zlib, libpng, and Cairo do contain support for compiling under VS10
-using VS project files and/or makefiles at this time of writing, For the
-GTK+ stack, VS10 project files are either available under
-$(srcroot)/build/vs10 in the case of GLib (stable/unstable), ATK**
-(2.x stable/unstable) and GDK-Pixbuf (unstable), and should be in the next
-unstable version of Pango.  There is no known official VS10 build
-support for fontconfig (along with freetype and expat) and
-gettext-runtime, so please use the binaries from: 
-
-ftp://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32 bit)
-ftp://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64 bit)
-
-Unzip the binaries obtained from ftp.gnome.org in <root>\vs10\<PlatformName>,
-and build the following, if not already done so: 
-
-Note: put the resulting zlib, libpng, pcre and Cairo files as follows:
- .dll files: <root>\vs10\<PlatformName>\bin
- .lib files: <root>\vs10\<PlatformName>\lib
- .h files: <root>\vs10\<PlatformName>\include
-
-The recommended build order for these dependencies:
-(first unzip any dependent binaries downloaded from the ftp.gnome.org
- as described in the README.txt file in the build/win32/vs10 folder)
--zlib
--libpng
--(for GDK-Pixbuf, if not using GDI+) IJG JPEG
--(for GDK-Pixbuf, if not using GDI+) libtiff
- [libtiff requires zlib and IJG JPEG]
--(for GDK-Pixbuf, if not using GDI+) jasper [jpeg-2000 library]
--(optional for GLib) PCRE (version 8.12 or later, use of CMake to
-  build PCRE is recommended-see build/win32/vs10/README.txt of GLib)
--GLib ***
--Cairo (inclusive of Cairo-GObject)
--ATK-2.x** ***
--Pango***
--GDK-Pixbuf***
-(note the last 3 dependencies are not interdependent, so the last 3
- dependencies can be built in any order)
-
-The "install" project will copy build results and headers into their
-appropriate location under <root>\vs10\<PlatformName>. For instance,
-built DLLs go into <root>\vs10\<PlatformName>\bin, built LIBs into
-<root>\vs10\<PlatformName>\lib and GTK+ headers into
-<root>\vs10\<PlatformName>\include\gtk-3.0. This is then from where
-project files higher in the stack are supposed to look for them, not
-from a specific GLib source tree.
-
-*About the dependencies marked with *: These dependencies are optional
- as those are not compulsory components for building and running GTK+
- itself, but note that they are needed for people running and building
- GIMP or those who need complex script support via fontconfig.  They
- are referred to by components in Cairo and Pango mainly.
- Decide whether you need fontconfig support prior to building Cairo
- and Pango.
- 
-**Regarding ATK-2.x: prior to compiling ATK-2.x, please open atkprops
-  in VS under "Properties Manager" view (it is under any one of the
-  build configurations, right-click on atkprops and select "Properties").
-  Navigate to "User Macros", and edit the following fields:
-  AtkApiVersion -> 2.0
-  AtkLibToolCompatibleDllSuffix -> -2.0-0
-  AtkSeperateVS10DLLSuffix -> -2-vs10
-  Sorry this change did not make it upstream prior to ATK-2.0.0 release-
-  this will be in the subsequent releases of ATK-2.x and was committed
-  upstream.
-
-***:Put the sources of the packages marked with *** in <root>\<package-
-    source-tree>, and build with VS10 from there.
-
---Tor Lillqvist <tml@iki.fi>
---Updated by Chun-wei Fan <fanc999@yahoo.com.tw>
+Note that all this is rather experimental.

+

+This VS10 solution and the projects it includes are intented to be used

+in a GTK+ source tree unpacked from a tarball. In a git checkout you

+first need to use some Unix-like environment or manual work to expand

+the files needed, like config.h.win32.in into config.h.win32 and the

+.vcprojin files here into corresponding actual .vcproj files.

+

+You will need the parts from below in the GTK+ stack: GDK-Pixbuf, Pango,

+ATK and GLib.  External dependencies are at least Cairo

+(with Cairo-GObject support, meaning Cairo 1.10.x or later), zlib, libpng,

+gettext-runtime, fontconfig*, freetype*, expat*.  See the 

+build/win32/vs10/README.txt file in glib for details where to unpack them.

+

+It is recommended that one builds the dependencies with VS10 as far as

+possible, especially those from and using the GTK+ stack (i.e. GLib,

+Cairo, ATK, Pango, GDK-Pixbuf), so that crashes caused by mixing calls

+to different CRTs can be kept at a minimum.

+

+zlib, libpng, and Cairo do contain support for compiling under VS10

+using VS project files and/or makefiles at this time of writing, For the

+GTK+ stack, VS10 project files are either available under

+$(srcroot)/build/vs10 in the case of GLib (stable/unstable), ATK**

+(2.x stable/unstable) and GDK-Pixbuf (unstable), and should be in the next

+unstable version of Pango.  There is no known official VS10 build

+support for fontconfig (along with freetype and expat) and

+gettext-runtime, so please use the binaries from: 

+

+ftp://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32 bit)

+ftp://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64 bit)

+

+Unzip the binaries obtained from ftp.gnome.org in <root>\vs10\<PlatformName>,

+and build the following, if not already done so: 

+

+Note: put the resulting zlib, libpng, pcre and Cairo files as follows:

+ .dll files: <root>\vs10\<PlatformName>\bin

+ .lib files: <root>\vs10\<PlatformName>\lib

+ .h files: <root>\vs10\<PlatformName>\include

+

+The recommended build order for these dependencies:

+(first unzip any dependent binaries downloaded from the ftp.gnome.org

+ as described in the README.txt file in the build/win32/vs10 folder)

+-zlib

+-libpng

+-(for GDK-Pixbuf, if not using GDI+) IJG JPEG

+-(for GDK-Pixbuf, if not using GDI+) libtiff

+ [libtiff requires zlib and IJG JPEG]

+-(for GDK-Pixbuf, if not using GDI+) jasper [jpeg-2000 library]

+-(optional for GLib) PCRE (version 8.12 or later, use of CMake to

+  build PCRE is recommended-see build/win32/vs10/README.txt of GLib)

+-GLib ***

+-Cairo (inclusive of Cairo-GObject)

+-ATK-2.x** ***

+-Pango***

+-GDK-Pixbuf***

+(note the last 3 dependencies are not interdependent, so the last 3

+ dependencies can be built in any order)

+

+The "install" project will copy build results and headers into their

+appropriate location under <root>\vs10\<PlatformName>. For instance,

+built DLLs go into <root>\vs10\<PlatformName>\bin, built LIBs into

+<root>\vs10\<PlatformName>\lib and GTK+ headers into

+<root>\vs10\<PlatformName>\include\gtk-3.0. This is then from where

+project files higher in the stack are supposed to look for them, not

+from a specific GLib source tree.

+

+*About the dependencies marked with *: These dependencies are optional

+ as those are not compulsory components for building and running GTK+

+ itself, but note that they are needed for people running and building

+ GIMP or those who need complex script support via fontconfig.  They

+ are referred to by components in Cairo and Pango mainly.

+ Decide whether you need fontconfig support prior to building Cairo

+ and Pango.

+ 

+**Regarding ATK-2.x: prior to compiling ATK-2.x, please open atkprops

+  in VS under "Properties Manager" view (it is under any one of the

+  build configurations, right-click on atkprops and select "Properties").

+  Navigate to "User Macros", and edit the following fields:

+  AtkApiVersion -> 2.0

+  AtkLibToolCompatibleDllSuffix -> -2.0-0

+  AtkSeperateVS10DLLSuffix -> -2-vs10

+  Sorry this change did not make it upstream prior to ATK-2.0.0 release-

+  this will be in the subsequent releases of ATK-2.x and was committed

+  upstream.

+

+***:Put the sources of the packages marked with *** in <root>\<package-

+    source-tree>, and build with VS10 from there.

+

+--Tor Lillqvist <tml@iki.fi>

+--Updated by Chun-wei Fan <fanc999@yahoo.com.tw>