-- 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.
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],
\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.
\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.