From 76704fd7a06fa97e2bf847db7464da7fb081444c Mon Sep 17 00:00:00 2001
From: Brian Carrier <carrier@sleuthkit.org>
Date: Mon, 27 Jan 2014 23:32:48 -0500
Subject: [PATCH] updated win32 building docs

---
 README_win32.txt   | 26 ++++++++++++++++----------
 win32/BUILDING.txt | 16 +++++++++++++++-
 2 files changed, 31 insertions(+), 11 deletions(-)

diff --git a/README_win32.txt b/README_win32.txt
index f9a8f726b..04183c31d 100644
--- a/README_win32.txt
+++ b/README_win32.txt
@@ -3,7 +3,7 @@
 
                 http://www.sleuthkit.org/sleuthkit
 
-                     Last Modified: Feb 2012
+                     Last Modified: Jan 2014
 
 ====================================================================
 The Sleuth Kit (TSK) runs on Windows.  If you simply want the
@@ -11,15 +11,21 @@ executables, you can download them from the www.sleuthkit.org
 website.
 
 If you want to build your own executables, you have two options.
-One is to use Microsoft Visual Studio.  The VS solution file is in
-the win32 directory.  Refer to the BUILDING.txt file in that directory
-for details.
-
-You can also compile Windows executables using mingw32.  If you're
-using mingw32 on Linux, simply give the "--host=i586-mingw32msvc"
-argument when running the './configure' script and use 'make' to
-compile.  If you're using mingw32 on Windows, './configure' and
-'make' will work directly.
+
+1) Microsoft Visual Studio.  The VS solution file is in the win32
+directory.  Refer to the win32\BUILDING.txt file for details for
+building the 32-bit and 64-bit versions. 
+
+2) mingw32.  See below for more details.
+
+
+---------------------------------------------------------------
+MINGW32
+
+If you're using mingw32 on Linux, simply give the
+"--host=i586-mingw32msvc" argument when running the './configure'
+script and use 'make' to compile.  If you're using mingw32 on Windows,
+'./configure' and 'make' will work directly.
 
 Note that to compile the Java bindings  you will need to have a JDK
 to be installed, and by default the Oracle JDK on Windows is installed
diff --git a/win32/BUILDING.txt b/win32/BUILDING.txt
index f0d04218e..47bc85b47 100755
--- a/win32/BUILDING.txt
+++ b/win32/BUILDING.txt
@@ -6,25 +6,39 @@ Visual Studio 2010 Express cannot make 64-bit versions of the executables.  To d
 
     http://msdn.microsoft.com/en-us/windowsserver/bb980924.aspx
 
+
+
 The Visual Studio Solution file has three build targets: Debug, Debug_NoLibs, and Release.  Debug and Release require that libewf exists (to provide support for E01 image files) and that zlib exists (to provide support for HFS+ compressed data).   Debug_NoLibs does not require libewf or zlib and you should be able to compile Debug_NoLibs without any additional setup.
 
+
+
 The steps below outline the process required to compile the Debug and Release targets.
 
-1) Download libewf-20130128 (or later) from:
+1) Download libewf-20130128 (or later).  The official releases are from:
     http://sourceforge.net/projects/libewf/
 
+If you want to build 64-bit libraries though, download a version that we've upgraded:
+    https://github.com/sleuthkit/libewf_64bit
+
+
 2) Open archive file and follow the README instructions in libewf to build libewf_dll (at the time of this writing, that includes downloading the zlib dll). Note that TSK will use only the Release version of libewf_dll.  Later steps also depend on the zlib dll being built inside of libewf.  Note that libewf will need to be converted to Visual Studio 2010 and be upgraded to support a 64-bit build.
 
+
 3) Set the LIBEWF_HOME environment variable to point to the libewf folder that you created and built in step 2. 
 
+
 4) If you want to build libtsk_jni for the Java JNI bindings, then set the JDK_HOME environment variable to point to the top directory of your Java SDK.
 
+
 5) Open the TSK Visual Studio Solution file, tsk-win.sln, in the win32 directory. 
 
+
 6) Compile a Debug, Debug_NoLibs, or Release version of the libraries and executables.  The resulting libraries and executables on a 32-bit build will be put in win32/Debug, win32/Debug_NoLibs, or win32/Release as appropriate.  A 64-bit build will put them into the win32/x64 folders. You can change the type of build using the pulldown in Visual Studio and switching between Win32 and x64.
 
+
 7) Note that the libraries and executables will depend on the libewf and zlib dll files (which are copied to the TSK build directories). 
 
+
 Refer to the API docs at http://sleuthkit.org/sleuthkit/docs/api-docs/ for details on how to use the library in an application.
 
 -------------------------------------------------------------------
-- 
GitLab