Clarified runtime linking issues.

1 files changed, 20 insertions, 6 deletions

diff --git a/win32/README.txt b/win32/README.txt
index 6e16b1c..2aba645 100644
--- a/win32/README.txt
+++ b/win32/README.txt
@@ -13,7 +13,7 @@ Expat can be built on Windows in three ways:
   Based on workspace (.dsw) and project files (.dsp)
   located in the lib subdirectory.
 
-* Special note about building static libraries under MS VC++:
+* Special note about MS VC++ and runtime libraries:
 
   There are three possible configurations: using the
   single threaded or multithreaded run-time library,
@@ -21,15 +21,29 @@ Expat can be built on Windows in three ways:
   one can build three different Expat libraries depending
   on the needs of the application.
 
+  Dynamic Linking:
+
+  By default the Expat Dlls are built to link with the
+  multi-threaded run-time Dll. The libraries are named
+  - libexpat(w).dll 
+  - libexpat(w).lib (import library)
+  The "w" indicates the UTF-16 version of the library.
+
+  One rarely uses other versions of the Dll, but they can
+  be built easily by specifying a different RTL linkage in
+  the IDE on the C/C++ tab under the category Code Generation.
+
+  Static Linking:
+
   The libraries should be named like this:
-  Single-theaded:     libexpatML.lib
-  Multi-threaded:     libexpatMT.lib
-  Multi-threaded Dll: libexpatMD.lib
+  Single-theaded:     libexpat(w)ML.lib
+  Multi-threaded:     libexpat(w)MT.lib
+  Multi-threaded Dll: libexpat(w)MD.lib
   The suffixes conform to the compiler switch settings
   /ML, /MT and /MD for MS VC++.
 
-  By default, the expat-static and expatw-static projects
-  are set up to link against the multithreaded run-time library,
+  By default, the expat-static and expatw-static projects are set up
+  to link dynamically against the multithreaded run-time library,
   so they will build libexpatMT.lib or libexpatwMT.lib files.
 
   To build the other versions of the static library,