view release on metacpan or  search on metacpan

unzip-6.0/INSTALL  view on Meta::CPAN

        distribution.
        Alternative compilers for the Intel platforms are OpenWatcom C++,
        GNU C (preferably the mingw32 port, CygWin and emx/rsxnt may also
        work), Borland C++, or lcc-win32.
        DEC C/C++ for NT/Alpha may or may not still work.
        For the Watcom compiler, use WMAKE and win32\makefile.wat; for the
        Microsoft compilers, use NMAKE and win32\Makefile; for mingw32 and
        CygWin, GNU Make and win32\Makefile.gcc should do the job.
        With emx+gcc, a good choice is GNUMake 3.75 (or higher) from the
        djgpp V2 distribution used on win32\Makefile.emx.

        The unzip32.dll WinDLL executables can be built using the appropiate
        Makefile in the win32\ subdirectory, or by using the Microsoft Visual
        C++ project files supplied below the windll subdirectory.  Besides the
        MSC compilers, gcc-mingw32, Watcom C and Borland C allow to build the
        Windows UnZip DLL.  By default, the Makefiles for compilers that use
        the Microsoft C runtime are configured to link against the shared
        multithreading C runtime DLL.  Depending on the intended usage for
        unzip32.dll, a statically linked dll might be more suitable.  The
        make scripts for MSC support build variants with static linking; you
        should look up the configuration switch DLLSTANDALONE in the MSC
        Makefile or the "Static..." build configurations in the Visual Studio
        project files.

      WinCE (WinCE or WinNT)
        Only Microsoft Visual C++ 5.0, 6.0 or Visual C++ embedded 3.0 or later
        are supported.  Use the appropiate version of the included project
        files and check wince\README for details.

      AmigaDOS
        SAS/Lattice C and Manx Aztec C are supported.  For SAS C 6.x do "smake
        -f amiga/smakefile all"; for Aztec C do "make -f amiga/makefile.azt
        all".  The Aztec C version supports assembly-language versions of two
        routines; these are enabled by default.

      Atari TOS
        Turbo C is no longer supported; use gcc and the MiNT libraries, and
        do "make".  Note that all versions of gcc prior to 2.5.8 have a bug
        affecting 68000-based machines (optimizer adds 68020 instructions).
        See atari\README for comments on using other compilers.

      Macintosh
        Metrowerks CodeWarrior Pro 4 with Universal Interfaces 3.1 is the only
        currently supported compiler, although the Mac Programmer's Workbench
        (MPW) and Think C were supported at one time and still have some hooks.
        Other Compilers may work too, no compiler specific instructions
        (pragma, header, macros, ...) were used in the code.
        For CodeWarrior Pro 4, un-BinHex the CodeWarrior project file and
        UnZip resource file (using Stuffit Expander or BinHex 4.0 or later),
        then open the project and click on the compile button.
        See ":macos:Contents" for the possible project targets.
        Link order of the standard libraries is very important: Link all
        sources first and all standard libraries last.

      Acorn (RISC OS)
        Extract the files from the archive and place in standard 'Acorn' C
        form (i.e., *.c, *.h and *.s become c.*, h.* and s.*, respectively),
        either using the UNZIP$EXTS environment variable and a pre-built UnZip
        binary, or using Spark[FS] and doing it manually.  Then copy the
        Acorn.Makefile to the main UnZip directory and either type 'amu' or
        use the desktop make utility.

      VM/CMS
        Unpack all the files and transfer them with ASCII -> EBCDIC conver-
        sion to an appropriate directory/minidisk/whatever, then execute
        UNZVMC to compile and link all the sources.  This may require C/370
        version 2.1 or later and certain `nucleus extensions,' although
        UnZip 5.3 has been reported to compile fine with the `ADCYCLE C/370
        v1.2 compiler.'  Note that it will abend without access to the C/370
        runtime library.  See the README.CMS file for more details.

      MVS
        Unpack all the files and transfer them to an appropriate PDS with
        ASCII -> EBCDIC conversion enabled, then edit UNZMVSC.JOB as required,
        and execute it to compile and link all the sources.  C/370 2.1 or
        later is required.  See README.MVS for further details.  [This is a
        new port and may need a little more work even to compile.]

      Human68K
        [This is a Japanese machine and OS.]  It appears that GNU make and
        gcc are required; presumably just do "gmake -f human68k/Makefile.gcc"
        to build everything.  This port has not been tested since the 5.12
        release.

      TOPS-20
        [No longer fully supported due to new, unported features, although
        patches are always accepted.]  Unpack all files into the current
        directory only (including those in the zipfile's tops20 directory),
        then use make.mic and "do make".

      BeOS
        You can run the BeOS makefile in place by typing "make -f
        beos/Makefile".  In fact, this is how the author tests it.

    Running the appropriate make utility should produce three executables on
    most systems, one for UnZip/ZipInfo, one for UnZipSFX, and one for fUnZip.
    (VMS is one prominent exception:  fUnZip makes no sense on it.  The Amiga
    produces a fourth executable called MakeSFX, which is necessary because
    Amiga self-extracting archives cannot be created by simple concatenation.
    If necessary the source amiga/makesfx.c can be compiled on other systems.)
    Read any OS-specific README files for notes on setting things up for
    normal use (especially for VMS) and for warnings about known quirks and
    bugs in various compilers (especially for MS-DOS).

    Also note that many OSes require a timezone variable to be set correctly
    (often "TZ"); Unix and VMS generally do so by default, Win95/NT do if set
    up properly, but other OSes generally do not.  See the discussion of the
    -f and -u options in the UnZip man page (or unzip.txt).  BeOS doesn't
    currently support timezone information at all, but this will probably be
    added soon.

    Then test your new UnZip on a few archives and let us know if there are
    problems (but *please* first make certain that the archives aren't actu-
    ally corrupted and that you didn't make one of the silly mistakes dis-
    cussed in the documentation).  If possible, double-check any problems
    with PKUNZIP or with a previous version of UnZip prior to reporting a
    "bug."  The zipfile itself may be damaged.



To install:

unzip-6.0/INSTALL  view on Meta::CPAN

      $ LIBRARY /CREATE /HELP UNZIP.HLB UNZIP.HLP

  UnZip help may then be accessed from a separate UnZip help library
  using a command like:

          $ HELP /LIBRARY = device:[directory]UNZIP.HLB

  For greater ease, the user (or system manager) may define a
  HLP$LIBRARY logical name to allow the HELP utility to find the UnZip
  help library automatically.  See HELP HELP /USERLIBRARY for more
  details.   The command procedure HLP_LIB_NEXT.COM may be used to
  determine the next available HLP$LIBRARY logical name, and could be
  adapted to define a HLP$LIBRARY logical name for an UnZip help library.

  The kit includes MAKESFX.COM, a command procedure intended to simplify
  creating a self-extracting archive.  It may be helpful to install this
  procedure near the UnZip executables.  MAKESFX.COM expects another
  symbol definition, like one of these:

     UNZIPSFX :== $ dev:[dir]UNZIPSFX.EXE       ! UNIX-like command line.
  or:
     UNZIPSFX :== $ dev:[dir]UNZIPSFX_CLI.EXE   ! VMS-like command line.

  Again here, on a non-VAX system, either a small-file or a large-file
  UNZIPSFX program may be used.  (MAKESFX.COM could be modified to allow
  a run-time choice to be made.)

OS/2, MS-DOS, NT, Atari, Amiga
  Move or copy unzip.exe (or unzip.ttp, or UnZip, or whatever) to a direc-
  tory in your path; also possibly copy the UnZip executable to zipinfo.exe
  (or ii.exe), or else create an alias or a batch/command file for ZipInfo
  ("@unzip -Z %1 %2 %3 %4 %5 %6 %7 %8 %9" under MS-DOS).  The latter is only
  relevant if NO_ZIPINFO was *not* defined, obviously...  Under djgpp 2.x,
  zipinfo.exe is a 2K stub symbolically linked to unzip.exe.

Acorn RISC OS
  Copy the executables unzip, funzip and zipinfo to somewhere in your
  Run$Path.  See your Welcome manual if you don't know about Run$Path.

BeOS
  The default prefix for the installation location is /boot/usr/local
  (things go into the bin and man/man1 subdirectories beneath the prefix),
  and the default man-page extension is "1" (corresponding to the man/man1,
  above).  Of course, these Unix man-pages aren't useful until someone ports
  something that can format them... plain text versions are also installed
  with an extension of ".txt".  To install, do a "make install", or to
  change the prefix, do "make prefix=/your/path install".  For example, to
  install in /boot/bin, do "make prefix=/boot/bin install".

Macintosh
  (This port is for Macintosh OS before Mac OS X.  See Unix Apple below for
  Mac OS X and later.)
  MacZip requires at least System 7 and a Macintosh with a minimum of a
  Motorola 68020 or PowerPC 601 processor. Other configurations may work
  but it is not tested at all.
  The application (MacZip) is distributed as a combination of zip and unzip
  in one program. The offical release is a fat binary with both regular 68K
  and native PowerPC versions included.
  Move the executable(s) somewhere--for example, drag it (or them) to your
  Applications folder.  For easy access, make an alias in the Launcher Control
  Panel or directly on your desktop.
  This port supports also Apple-event.So you can install it in your
  WWW-Browser as a helper-app.
  Look into "macos/README.TXT" (or ":macos:README.TXT" on Mac) for further
  info.

Macintosh OS X (Unix Apple)
  Mac OS X and later are based on BSD Unix and are supported by the Unix
  port.  See the Unix port for details.  Though support is currently
  minimal, we plan to support additional Mac OS X features, such as resource
  forks, in future releases.

Human68K, TOPS-20, AOS/VS, MVS, VM/CMS, etc.
  Dunno, sorry...