[json-glib] Added README.txt's for Visual Studio support

[Chun-wei Fan <fanchunwei src gnome org>]

commit 75e370e53cb5d31d4a366fc5f126583872f1349a
Author: Chun-wei Fan <fanchunwei src gnome org>
Date:   Wed Jun 29 14:29:12 2011 +0800

    Added README.txt's for Visual Studio support
    
    Added README.txt's and included them in distribution to tell
    people how JSON-GLib can be build on Windows using Visual C++.

 build/win32/vs10/Makefile.am |    1 +
 build/win32/vs10/README.txt  |   87 ++++++++++++++++++++++++++++++++++++++++++
 build/win32/vs9/Makefile.am  |    1 +
 build/win32/vs9/README.txt   |   86 +++++++++++++++++++++++++++++++++++++++++
 4 files changed, 175 insertions(+), 0 deletions(-)
---
diff --git a/build/win32/vs10/Makefile.am b/build/win32/vs10/Makefile.am
index d4bb721..72bd7b0 100644
--- a/build/win32/vs10/Makefile.am
+++ b/build/win32/vs10/Makefile.am
@@ -34,4 +34,5 @@ EXTRA_DIST =	\
 	serialize-full.vcxproj.filters	\
 	serialize-simple.vcxproj	\
 	serialize-simple.vcxproj.filters	\
+	README.txt	\
 	$(NULL)
diff --git a/build/win32/vs10/README.txt b/build/win32/vs10/README.txt
new file mode 100644
index 0000000..e3ced34
--- /dev/null
+++ b/build/win32/vs10/README.txt
@@ -0,0 +1,87 @@
+This VS10 solution and the projects it includes are intended to be used
+in a JSON-GLib 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 .in files needed, mainly config.h.win32.in into config.h.win32.
+You will also need to expand json-glib.vcxprojin and json-glib.vcxproj.filtersin
+here into json-glib.vcxproj and json-glib.vcxproj.filters repectively.
+
+The dependencies for this package are gettext-runtime (libintl), GLib*,
+ZLib at the minimum.
+
+For the Dependencies, you may either:
+
+a) look for all of the dependencies (except GLib*) under
+
+   http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32-bit) -OR-
+   http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64-bit)
+
+   Please use the latest versions of these libraries that are available there,
+   these are packaged by Tor Lillqvist, which are built with MinGW/GCC.
+   Please see b) below regarding the build of GLib*
+
+-OR-
+
+b) Build them yourself with VS10 (but you may most probably wish to get
+   gettext-runtime from the URL(s) mentioned in a)).  Use the latest
+   stable versions for them (you may need to get the latest unstable version of
+   GLib if you are using an unstable version of JSON-GLib):
+
+   GLib*:   Grab the latest sources from http://www.gtk.org under "Download"
+            (stable only-please make a search for the latest unstable versions)
+   ZLib:   http://www.zlib.net
+
+   The above 2 packages all have supported mechanisms (Makefiles and/or Project
+   Files) for building under VS10 (upgrade the Project Files from earlier VS
+   versions will do for these, when applicable).  It is recommended that ZLib
+   is built using the win32/Makefile.msc makefile with VS10 with the ASM routines
+   to avoid linking problems (copy zdll.lib to zlib1.lib[Release] or to zlib1d.lib
+   [Debug] after completion of compilation)-see win32/Makefile.msc in ZLib for
+   more details.
+
+* This GLib refers to a build that is built by VS10
+
+Set up the source tree as follows under some arbitrary top
+folder <root>:
+
+<root>\json-glib\<this-json-glib-source-tree>
+<root>\vs10\<PlatformName>
+
+*this* file you are now reading is thus located at
+<root>\json-glib\<this-json-glib-source-tree>\build\win32\vs10\README.
+
+<PlatformName> is either Win32 or x64, as in the VS10 project files.
+
+You should unpack the <dependent-package>-dev and <dependent-packge> (runtime)
+into <root>\vs10\<PlatformName>, if you download any of the packages from
+
+http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32-bit) -OR-
+http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64-bit)
+
+so that for instance libintl.h end up at 
+<root>\vs10\<PlatformName>\include\libintl.h.
+
+If you build any of the dependencies yourselves, copy the: 
+-DLLs and EXEs into <root>\vs10\<PlatformName>\bin
+-headers into <root>\vs10\<PlatformName>\include\
+-LIBs into <root>\vs10\<PlatformName>\lib
+
+If you have not built GLib with VS10 and placed the LIBs and headers in a
+place where VS10 can find them automatically, you should also uncompress
+your GLib sources in <root>\ and build it from there, following the
+instructions in <root>\glib<-version>\build\win32\vs10, so that the required
+headers, EXEs, DLLs and LIBs will end up in
+<root>\vs10\<PlatformName>\include\glib-2.0 (headers)
+<root>\vs10\<PlatformName>\lib (LIBs, also glib-2.0/include/glibconfig.h)
+<root>\vs10\<PlatformName>\bin (EXEs/DLLs)
+respectively.
+
+After the build of JSON-GLib, 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 JSON-GLib headers into
+<root>\vs10\<PlatformName>\include\json-glib-1.0. This is then from where
+project files higher in the stack are supposed to look for them, not
+from a specific JSON-GLib source tree.
+
+--Chun-wei Fan <fanc999 yahoo com tw>
+--(adapted from the GLib VS9 README.txt file originally written by Tor Lillqvist)
diff --git a/build/win32/vs9/Makefile.am b/build/win32/vs9/Makefile.am
index 426beb2..b8cb751 100644
--- a/build/win32/vs9/Makefile.am
+++ b/build/win32/vs9/Makefile.am
@@ -19,4 +19,5 @@ EXTRA_DIST =	\
 	serialize-complex.vcproj	\
 	serialize-full.vcproj		\
 	serialize-simple.vcproj		\
+	README.txt			\
 	$(NULL)
diff --git a/build/win32/vs9/README.txt b/build/win32/vs9/README.txt
new file mode 100644
index 0000000..53bfd95
--- /dev/null
+++ b/build/win32/vs9/README.txt
@@ -0,0 +1,86 @@
+This VS9 solution and the projects it includes are intended to be used
+in a JSON-GLib 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 .in files needed, mainly config.h.win32.in into config.h.win32.
+You will also need to expand json-glib.vcprojin here into json-glib.vcproj.
+
+The dependencies for this package are gettext-runtime (libintl), GLib*,
+ZLib at the minimum.
+
+For the Dependencies, you may either:
+
+a) look for all of the dependencies (except GLib*) under
+
+   http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32-bit) -OR-
+   http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64-bit)
+
+   Please use the latest versions of these libraries that are available there,
+   these are packaged by Tor Lillqvist, which are built with MinGW/GCC.
+   Please see b) below regarding the build of GLib*
+
+-OR-
+
+b) Build them yourself with VS9 (but you may most probably wish to get
+   gettext-runtime from the URL(s) mentioned in a)).  Use the latest
+   stable versions for them (you may need to get the latest unstable version of
+   GLib if you are using an unstable version of JSON-GLib):
+
+   GLib*:   Grab the latest sources from http://www.gtk.org under "Download"
+            (stable only-please make a search for the latest unstable versions)
+   ZLib:   http://www.zlib.net
+
+   The above 2 packages all have supported mechanisms (Makefiles and/or Project
+   Files) for building under VS9 (upgrade the Project Files from earlier VS
+   versions will do for these, when applicable).  It is recommended that ZLib
+   is built using the win32/Makefile.msc makefile with VS9 with the ASM routines
+   to avoid linking problems (copy zdll.lib to zlib1.lib[Release] or to zlib1d.lib
+   [Debug] after completion of compilation)-see win32/Makefile.msc in ZLib for
+   more details.
+
+* This GLib refers to a build that is built by VS9
+
+Set up the source tree as follows under some arbitrary top
+folder <root>:
+
+<root>\json-glib\<this-json-glib-source-tree>
+<root>\vs9\<PlatformName>
+
+*this* file you are now reading is thus located at
+<root>\json-glib\<this-json-glib-source-tree>\build\win32\vs9\README.
+
+<PlatformName> is either Win32 or x64, as in the VS9 project files.
+
+You should unpack the <dependent-package>-dev and <dependent-packge> (runtime)
+into <root>\vs9\<PlatformName>, if you download any of the packages from
+
+http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32-bit) -OR-
+http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64-bit)
+
+so that for instance libintl.h end up at 
+<root>\vs9\<PlatformName>\include\libintl.h.
+
+If you build any of the dependencies yourselves, copy the: 
+-DLLs and EXEs into <root>\vs9\<PlatformName>\bin
+-headers into <root>\vs9\<PlatformName>\include\
+-LIBs into <root>\vs9\<PlatformName>\lib
+
+If you have not built GLib with VS9 and placed the LIBs and headers in a
+place where VS9 can find them automatically, you should also uncompress
+your GLib sources in <root>\ and build it from there, following the
+instructions in <root>\glib<-version>\build\win32\vs9, so that the required
+headers, EXEs, DLLs and LIBs will end up in
+<root>\vs9\<PlatformName>\include\glib-2.0 (headers)
+<root>\vs9\<PlatformName>\lib (LIBs, also glib-2.0/include/glibconfig.h)
+<root>\vs9\<PlatformName>\bin (EXEs/DLLs)
+respectively.
+
+After the build of JSON-GLib, the "install" project will copy build results
+and headers into their appropriate location under <root>\vs9\<PlatformName>.
+For instance, built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into
+<root>\vs9\<PlatformName>\lib and JSON-GLib headers into
+<root>\vs9\<PlatformName>\include\json-glib-1.0. This is then from where
+project files higher in the stack are supposed to look for them, not
+from a specific JSON-GLib source tree.
+
+--Chun-wei Fan <fanc999 yahoo com tw>
+--(adapted from the GLib VS9 README.txt file originally written by Tor Lillqvist)