From a381a9e10a60c7790fe33255c949bf55b5872a8d Mon Sep 17 00:00:00 2001 From: Eric Biggers Date: Sun, 10 Mar 2013 14:51:25 -0500 Subject: [PATCH] Doc fixes --- TODO | 7 ++++--- configure.ac | 3 +++ doc/imagex-apply.1.in | 4 ++-- doc/imagex-capture.1.in | 2 +- 4 files changed, 10 insertions(+), 6 deletions(-) diff --git a/TODO b/TODO index 149d4e33..8fc45af3 100644 --- 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 5f962f38..cb41ba18 100644 --- 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 5197f78f..d60c53d6 100644 --- 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 a35179ce..38c462aa 100644 --- 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. -- 2.43.0