libmspack 0.0.5 → 0.10.1.2

data/ext/libmspack/README

@@ -1,4 +1,4 @@
-libmspack 0.4alpha
+libmspack 0.10.1alpha
 
 The purpose of libmspack is to provide compressors and decompressors,
 archivers and dearchivers for Microsoft compression formats: CAB, CHM, WIM,
@@ -24,7 +24,7 @@ DOCUMENTATION
 
 The API documentation is stored in the doc/ directory. It is generated
 automatically from mspack.h with doxygen. It is also available online at
-http://www.cabextract.org.uk/libmspack/doc/
+https://www.cabextract.org.uk/libmspack/doc/
 
 
 BUILDING / INSTALLING
@@ -36,15 +36,14 @@ make install
 This will install the main libmspack library and mspack.h header file.
 Some other libraries and executables are built, but not installed.
 
-If building from the Subversion repository, running rebuild.sh will create
-all the automatically generated files like the configure script, and will
-then ./configure, make and make distcheck. Running cleanup.sh will perform
-a thorough clean, deleting all automatically generated files.
+If building from the Git repository, running rebuild.sh will create all the
+auto-generated files, then run ./configure && make. Running cleanup.sh will
+perform a thorough clean, deleting all auto-generated files.
 
-In addition to gcc, you also need the following for building from Subversion:
+In addition to gcc, you also need the following for building from repository:
 
 - at least autoconf 2.57
-- at least automake 1.7
+- at least automake 1.11
 - libtool
 
 This is an alpha release. Unless you are in a position to package the
@@ -56,7 +55,7 @@ source files directly in your application's build environment.
 
 LEGAL ISSUES
 
-The the best of my knowledge, libmspack does not infringe on any
+To the best of my knowledge, libmspack does not infringe on any
 compression or decompression patents. However, this is not legal
 advice, and it is recommended that you perform your own patent search.
 
@@ -78,27 +77,28 @@ provided you meet ALL of the following conditions:
 
 EXAMPLE CODE
 
-There are a number of useful programs in the test/ directory which
-exercise and demonstrate libmspack's features.
-
-cabd_c10       - Tests the CAB decompressor on the C10 collection.
-cabd_compare   - Compares the CAB decompressor with Microsoft's EXTRACT.EXE
-cabd_md5       - Prints the MD5 checksums of all files within a CAB file/set.
-cabd_memory    - An mspack_system implementation that reads/writes to memory.
-cabd_test      - Regression tests for libmspack's CAB decompression.
-cabrip         - Extracts any CAB files embedded in another file.
-chmd_compare   - Compares the CHM decompressor to Microsoft's HH.EXE
-chmd_find      - Fast-finds a file within a CHM file.
-chmd_md5       - Prints the MD5 checksums of all files within a CHM file.
-chmd_order     - Tests extracting files in a CHM file in four different ways.
-chminfo        - Prints verbose information about CHM file structures.
-chmx           - Extracts all files in a CHM file to disk.
-expand         - Extracts an SZDD or KWAJ file.
-msdecompile_md5- Runs Microsoft's HH.EXE -DECOMPILE via WINE.
-msexpand_md5   - Runs Microsoft's EXTRACT.EXE via WINE.
-multifh        - An mspack_system implementation that can simultaneously work
-                 on in-memory images, raw file descriptors, open file handles
-                 and regular disk files.
+libmspack is bundled with programs which demonstrate the library's features.
+
+examples/cabd_memory.c - an mspack_system that can read and write to memory
+examples/multifh.c     - an mspack_system that can simultaneously work on
+                         in-memory images, raw file descriptors, open file
+                         handles and regular disk files
+
+examples/cabrip.c       - extracts any CAB files embedded in another file
+examples/chmextract.c   - extracts all files in a CHM file to disk
+examples/msexpand.c     - expands an SZDD or KWAJ file
+examples/oabextract.c   - extracts an Exchange Offline Address Book (.LZX) file
+
+test/cabd_c10          - tests the CAB decompressor on the C10 collection
+test/cabd_compare      - compares libmspack with Microsoft's EXTRACT.EXE
+test/cabd_md5          - shows MD5 checksums of all files in a CAB file/set
+test/chmd_compare      - compares libmspack with Microsoft's HH.EXE
+test/chmd_find.c       - checks all files in a CHM file can be fast-found
+test/chmd_md5.c        - shows MD5 checksums of all files within a CHM file
+test/chmd_order.c      - extracts files in a CHM file in four different ways
+test/chminfo.c         - prints verbose information about CHM file structures
+test/msdecompile_md5   - runs Microsoft's HH.EXE -DECOMPILE via WINE
+test/msextract_md5     - runs Microsoft's EXTRACT.EXE via WINE
 
 Here is a simple example of usage, which will create a CAB decompressor,
 then use that to open an existing Microsoft CAB file called "example.cab",

data/ext/libmspack/acinclude.m4

@@ -0,0 +1,99 @@
+# ===========================================================================
+#      https://www.gnu.org/software/autoconf-archive/ax_func_mkdir.html
+# ===========================================================================
+#
+# SYNOPSIS
+#
+#   AX_FUNC_MKDIR
+#
+# DESCRIPTION
+#
+#   Check whether mkdir() is mkdir or _mkdir, and whether it takes one or
+#   two arguments.
+#
+#   This macro can define HAVE_MKDIR, HAVE__MKDIR, and MKDIR_TAKES_ONE_ARG,
+#   which are expected to be used as follows:
+#
+#     #if HAVE_MKDIR
+#     #  if MKDIR_TAKES_ONE_ARG
+#          /* MinGW32 */
+#     #    define mkdir(a, b) mkdir(a)
+#     #  endif
+#     #else
+#     #  if HAVE__MKDIR
+#          /* plain Windows 32 */
+#     #    define mkdir(a, b) _mkdir(a)
+#     #  else
+#     #    error "Don't know how to create a directory on this system."
+#     #  endif
+#     #endif
+#
+# LICENSE
+#
+#   Copyright (c) 2008 Alexandre Duret-Lutz <adl@gnu.org>
+#
+#   This program is free software; you can redistribute it and/or modify it
+#   under the terms of the GNU General Public License as published by the
+#   Free Software Foundation; either version 2 of the License, or (at your
+#   option) any later version.
+#
+#   This program is distributed in the hope that it will be useful, but
+#   WITHOUT ANY WARRANTY; without even the implied warranty of
+#   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
+#   Public License for more details.
+#
+#   You should have received a copy of the GNU General Public License along
+#   with this program. If not, see <https://www.gnu.org/licenses/>.
+#
+#   As a special exception, the respective Autoconf Macro's copyright owner
+#   gives unlimited permission to copy, distribute and modify the configure
+#   scripts that are the output of Autoconf when processing the Macro. You
+#   need not follow the terms of the GNU General Public License when using
+#   or distributing such scripts, even though portions of the text of the
+#   Macro appear in them. The GNU General Public License (GPL) does govern
+#   all other use of the material that constitutes the Autoconf Macro.
+#
+#   This special exception to the GPL applies to versions of the Autoconf
+#   Macro released by the Autoconf Archive. When you make and distribute a
+#   modified version of the Autoconf Macro, you may extend this special
+#   exception to the GPL to apply to your modified version as well.
+
+#serial 6
+
+AU_ALIAS([AC_FUNC_MKDIR], [AX_FUNC_MKDIR])
+AC_DEFUN([AX_FUNC_MKDIR],
+[AC_CHECK_FUNCS([mkdir _mkdir])
+AC_CACHE_CHECK([whether mkdir takes one argument],
+               [ac_cv_mkdir_takes_one_arg],
+[AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[
+#include <sys/stat.h>
+#if HAVE_UNISTD_H
+#  include <unistd.h>
+#endif
+]], [[mkdir (".");]])],
+[ac_cv_mkdir_takes_one_arg=yes], [ac_cv_mkdir_takes_one_arg=no])])
+if test x"$ac_cv_mkdir_takes_one_arg" = xyes; then
+  AC_DEFINE([MKDIR_TAKES_ONE_ARG], 1,
+            [Define if mkdir takes only one argument.])
+fi
+])
+
+dnl Note:
+dnl =====
+dnl I have not implemented the following suggestion because I don't have
+dnl access to such a broken environment to test the macro.  So I'm just
+dnl appending the comments here in case you have, and want to fix
+dnl AX_FUNC_MKDIR that way.
+dnl
+dnl |Thomas E. Dickey (dickey@herndon4.his.com) said:
+dnl |  it doesn't cover the problem areas (compilers that mistreat mkdir
+dnl |  may prototype it in dir.h and dirent.h, for instance).
+dnl |
+dnl |Alexandre:
+dnl |  Would it be sufficient to check for these headers and #include
+dnl |  them in the AC_COMPILE_IFELSE block?  (and is AC_HEADER_DIRENT
+dnl |  suitable for this?)
+dnl |
+dnl |Thomas:
+dnl |  I think that might be a good starting point (with the set of recommended
+dnl |  ifdef's and includes for AC_HEADER_DIRENT, of course).