Revert README.txt line endings to CRLF

1 files changed, 61 insertions, 61 deletions

diff --git a/win32/README.txt b/win32/README.txt
index ed76899..4dbdd14 100755
--- a/win32/README.txt
+++ b/win32/README.txt
@@ -1,61 +1,61 @@
-I. INTRODUCTION
-===============
-
-Hello, and welcome to the Windows build instructions for asdcplib.
-
-
-II. DEPENDENCIES
-================
-
-First, you'll need Microsoft's Visual Studio 2005 or later. A heavyweight edition isn't needed;
-the freely downloadable Express edition works fine.
-
-Next, you'll need an OpenSSL distribution. The absolute, bare minimum needed is 0.9.7. However,
-if this will be used in conjunction with CineCert's other software, the later 0.9.8b
-is needed. That said, the latest revision of OpenSSL as of this writing (0.9.8j) works great.
-Extract and build in the directory of your choice.
-
-For optional XML parsing support, you'll need to use Xerces-C++ 2.7 or 3.x, or Expat 2.0.1
-(supported in previous versions of asdcplib). If you'll be using this software in conjuction with
-CineCert's other software, the use of Xerces-C++ is required. As with OpenSSL above, if you
-need/desire XML parsing, extract the source package and build in a directory of your choice.
-
-Header files and libraries from the OpenSSL and XML packages must be available to the compiler
-and linker. You may need to modify the makefile to make include files (/I...) and library files
-(/LIBPATH...) available.
-
-
-III. BUILDING
-=============
-
-There's a build option that changes the behavior of UUID generation. If ENABLE_RANDOM_UUID is
-set at build, then mixed-case UUID generation will be enabled if (and only if) the environment
-variable KM_USE_RANDOM_UUID is set during runtime.
-
-Open a command prompt in which the VS build tools are available on the command line (e.g., the
-"Visual Studio command prompt"). The nmake invocation follows this form:
-C:\>nmake WITH_OPENSSL=<OpenSSL directory> [WITH_XERCES=<Xerces directory>|
-	WITH_XML_PARSER=<Expat directory>] [ENABLE_RANDOM_UUID=1] /f Makefile32.wmk
-
-On our Windows development machine, the invocation with XML parsing by Xerces-C++ is as such:
-C:\Program Files (x86)\asdcplib\win32>nmake WITH_OPENSSL="C:\Program Files (x86)\openssl"
-	WITH_XERCES="C:\Program Files (x86)\xerces-c" /f Makefile32.wmk
-
-With XML parsing by Expat and random UUID generation enabled:
-C:\Program Files (x86)\asdcplib\win32>nmake WITH_OPENSSL="C:\Program Files (x86)\openssl"
-	WITH_XML_PARSER="C:\Program Files (x86)\Expat 2.0.1" ENABLE_RANDOM_UUID=1 /f Makefile32.wmk
-
-Without XML parsing:
-C:\Program Files (x86)\asdcplib\win32>nmake WITH_OPENSSL="C:\Program Files (x86)\openssl"
-	/f Makefile32.wmk
-
-Without XML parsing but with the AS-02 library and executables:
-C:\Program Files (x86)\asdcplib\win32>nmake WITH_OPENSSL="C:\Program Files (x86)\openssl"
-	USE_AS_02=1 /f Makefile32.wmk
-
-Want a 64-bit build? Use Makefile64.wmk and specify 64-bit library locations.
-
-IV. CONCLUSION
-==============
-
-For answers to questions, please send a message to <asdcplib@cinecert.com>.
+I. INTRODUCTION

+===============

+

+Hello, and welcome to the Windows build instructions for asdcplib.

+

+

+II. DEPENDENCIES

+================

+

+First, you'll need Microsoft's Visual Studio 2005 or later. A heavyweight edition isn't needed;

+the freely downloadable Express edition works fine.

+

+Next, you'll need an OpenSSL distribution. The absolute, bare minimum needed is 0.9.7. However,

+if this will be used in conjunction with CineCert's other software, the later 0.9.8b

+is needed. That said, the latest revision of OpenSSL as of this writing (0.9.8j) works great.

+Extract and build in the directory of your choice.

+

+For optional XML parsing support, you'll need to use Xerces-C++ 2.7 or 3.x, or Expat 2.0.1

+(supported in previous versions of asdcplib). If you'll be using this software in conjuction with

+CineCert's other software, the use of Xerces-C++ is required. As with OpenSSL above, if you

+need/desire XML parsing, extract the source package and build in a directory of your choice.

+

+Header files and libraries from the OpenSSL and XML packages must be available to the compiler

+and linker. You may need to modify the makefile to make include files (/I...) and library files

+(/LIBPATH...) available.

+

+

+III. BUILDING

+=============

+

+There's a build option that changes the behavior of UUID generation. If ENABLE_RANDOM_UUID is

+set at build, then mixed-case UUID generation will be enabled if (and only if) the environment

+variable KM_USE_RANDOM_UUID is set during runtime.

+

+Open a command prompt in which the VS build tools are available on the command line (e.g., the

+"Visual Studio command prompt"). The nmake invocation follows this form:

+C:\>nmake WITH_OPENSSL=<OpenSSL directory> [WITH_XERCES=<Xerces directory>|

+	WITH_XML_PARSER=<Expat directory>] [ENABLE_RANDOM_UUID=1] /f Makefile32.wmk

+

+On our Windows development machine, the invocation with XML parsing by Xerces-C++ is as such:

+C:\Program Files (x86)\asdcplib\win32>nmake WITH_OPENSSL="C:\Program Files (x86)\openssl"

+	WITH_XERCES="C:\Program Files (x86)\xerces-c" /f Makefile32.wmk

+

+With XML parsing by Expat and random UUID generation enabled:

+C:\Program Files (x86)\asdcplib\win32>nmake WITH_OPENSSL="C:\Program Files (x86)\openssl"

+	WITH_XML_PARSER="C:\Program Files (x86)\Expat 2.0.1" ENABLE_RANDOM_UUID=1 /f Makefile32.wmk

+

+Without XML parsing:

+C:\Program Files (x86)\asdcplib\win32>nmake WITH_OPENSSL="C:\Program Files (x86)\openssl"

+	/f Makefile32.wmk

+

+Without XML parsing but with the AS-02 library and executables:

+C:\Program Files (x86)\asdcplib\win32>nmake WITH_OPENSSL="C:\Program Files (x86)\openssl"

+	USE_AS_02=1 /f Makefile32.wmk

+

+Want a 64-bit build? Use Makefile64.wmk and specify 64-bit library locations.

+

+IV. CONCLUSION

+==============

+

+For answers to questions, please send a message to <asdcplib@cinecert.com>.