Documentation update.

msvc/README-MSVC.txt

@@ -1,15 +1,17 @@
 Notes about msvc 32 bit build of exiv2
 --------------------------------------
 
-+------------------------------------------------------+
++----------------------------------------------------------+
 | This version of the build environment builds 32 bit      |
 | builds of exiv2 for DevStudio 2003 (VS7.1) and later     |
 |                                                          |
-| Please use the project files in msvc64 for 32 and 64 |
+| VS2003 USERS: Use project/sln in this directory to build |
-| bit builds in VS2005 and later.                      |
+| VS2005 USERS: Please use msvc64 (even for 32 bit builds) |
+| VS2008 USERS: Please use msvc64 (even for 32 bit builds) |
+| VS2010 USERS: Use msvc64 for all builds                  |
 |                                                          |
 | Please see msvc64\ReadMe.txt for more information        |
-+------------------------------------------------------+
++----------------------------------------------------------+
 
 Tools
 -----
@@ -152,6 +154,12 @@ How to build and test exiv2 (with/without organize.exe)
     
     The test takes less than 1 minute and runs 200+ different test programs.
     
+7)  Running the test suite
+
+    The test suite is a collection of bash scripts and requires a unix-like environment
+    in which to run.  exiv2 msvc and msvc64 builds are tested with cygwin and msys.
+    Please see the file exiv2/msvc64/ReadMe.txt for more information.
+    
 How to build exiv2+organize
 ---------------------------
 
@@ -410,4 +418,5 @@ D) Boost library name conventions
     .lib
     Extension: determined according to the operating system's usual convention. On most unix-style platforms the extensions are .a and .so for static libraries (archives) and shared libraries, respectively. On Windows, .dll indicates a shared library and (except for static libraries built by the gcc toolset, whose names always end in .a) .lib indicates a static or import library. Where supported by toolsets on unix variants, a full version extension is added (e.g. ".so.1.34") and a symbolic link to the library file, named without the trailing version number, will also be created.
 
--- end --
+# That's all Folks
+##

msvc64/ReadMe.txt

@@ -6,7 +6,7 @@ exiv2\msvc64\ReadMe.txt
 | the msvc   environment only builds 32bit                  |
 +-----------------------------------------------------------+
 
-Updated: 2012-05-05 
+Updated: 2012-05-07 
 
 Robin Mills
 http://clanmills.com
@@ -274,12 +274,23 @@ T A B L E  o f  C O N T E N T S
 			    make test
 			done
 			
-	I recommend running listdlls exiv2.exe occasionally during testing to be confident that
+	Free gift: (you get what you pay for)
-	the test suite is running the MSVC built versions of exiv2 and libraries.
+			The script testMSVC.sh to runs this loop for you.
+			The script verifyMSVC.sh validates the output of testMSVC.sh
+			I've added those for my convenience and I hope you'll find them useful.
+
+	And to pass the time (the test suite takes about an hour to run)
+			I recommend running listdlls exiv2.exe occasionally during testing to be confident
+			that the test suite is running the MSVC built versions of exiv2 and libraries.
+			
+			From cygwin:
+			while sleep 1 do; listdlls exiv2.exe ; done
+			or
+			while sleep 10 do ; listdlls exiv2.exe | grep exiv2.exe ; done
 			
 	Note: Cygwin currently ships diff-utils 2.9.2 which treats binary files differently
 	from 2.8.7 (on Mac) and 3.2 (on Ubuntu 12.04).  For this reason, the executable (and
-	support dlls for GNU diff.exe 2.8.7 is provided in msvc/diff.exe.
+	support dlls) for GNU diff.exe 2.8.7 is provided in msvc/diff.exe.
 	The test suite has been "doctored" on cygwin to modify the path appropriately to
 	use this preferred version of diff.exe.