Doc fixes

diff --git a/TODO b/TODO
index 149d4e335c0b5e50fe840a14cc0618bbcd05e1c1..8fc45af382d550ced01da528abb263fbc65cdb50 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,3 +1,4 @@
-- Fix bugs
-- Add more test cases
-- Implement LZX block splitting to improve compression ratio
+- Find and fix bugs
+- Add more test cases (including for Win32 builds)
+- Improve LZX compression ratio, possibly by implementing LZX block splitting
+  and/or by improving the LZ77 match-finding code.

diff --git a/configure.ac b/configure.ac
index 5f962f38eab21e09625eb8e8fb8eef237829c89d..cb41ba188f8061243763e41ab5da6f119fb77f96 100644 (file)
--- a/configure.ac
+++ b/configure.ac
@@ -182,17 +182,20 @@ case "$host" in
 
                WITH_NTFS_3G_DEFAULT="no"
                WITH_FUSE_DEFAULT="no"
+               WINDOWS_BUILD="yes"
                ;;
        *)
                CYGWIN_EXTRA_LDFLAGS=""
                VISIBILITY_CFLAGS="-fvisibility=hidden"
                WITH_NTFS_3G_DEFAULT="yes"
                WITH_FUSE_DEFAULT="yes"
+               WINDOWS_BUILD="no"
                ;;
 esac
 
 AC_SUBST([CYGWIN_EXTRA_LDFLAGS], [$CYGWIN_EXTRA_LDFLAGS])
 AC_SUBST([VISIBILITY_CFLAGS], [$VISIBILITY_CFLAGS])
+AM_CONDITIONAL([WINDOWS_BUILD], [test "x$WINDOWS_BUILD" = "xyes"])
 
 AC_MSG_CHECKING([whether to include support for ntfs-3g])
 AC_ARG_WITH([ntfs-3g],

diff --git a/doc/imagex-apply.1.in b/doc/imagex-apply.1.in
index 5197f78f8e537c2ec19ace71c7944cfd4ec838af..d60c53d64acbc6386c92b1fca3e2b9e61086b81b 100644 (file)
--- a/doc/imagex-apply.1.in
+++ b/doc/imagex-apply.1.in
@@ -201,8 +201,8 @@ UNIX version.
 
 \fBimagex apply\fR does not have separate "normal" and "NTFS" modes on Windows.
 There is simply one mode, and it uses the Windows API to apply NTFS-specific
-information, including alternate data streams, reparse points, hard link, and
-symbolic links.  So, you essentially get the advantages of the "NTFS mode"
+information, including alternate data streams, reparse points, hard links, and
+file attributes.  So, you essentially get the advantages of the "NTFS mode"
 documented above, but you can apply the WIM image to any directory, not just an
 entire NTFS volume.  This is mostly the same behavior as Microsoft's ImageX.
 

diff --git a/doc/imagex-capture.1.in b/doc/imagex-capture.1.in
index a35179ce04fa079fd159f11c662ada0061ea3b85..38c462aa1460f7f2c84cb4c9fa336e1327a3555c 100644 (file)
--- a/doc/imagex-capture.1.in
+++ b/doc/imagex-capture.1.in
@@ -118,7 +118,7 @@ page, which is written to document UNIX version.
 \fBimagex capture\fR and \fBimagex append\fR do not have separate "normal" and
 "NTFS" modes on Windows.  There is simply one mode, and it uses the Windows API
 to capture NTFS-specific information, including alternate data streams, reparse
-points, hard link, and symbolic links.  So, you essentially get the advantages
+points, hard links, and file attributes.  So, you essentially get the advantages
 of the "NTFS mode" documented above, but you can capture a WIM image from any
 directory, not just an entire NTFS volume.  This is mostly the same behavior as
 Microsoft's ImageX.