This is a port of LAME 3.100 to MSDOS/DJGPP.

  LAME is a program which can be used to create compressed audio files.
  (Lame ain't an MP3 encoder).  These audio files can be played back by
  popular MP3 players such as mpg123 or madplay.



1.:     DJGPP specific changes.
        =======================

      - This port has been configured to be build in the "0build" directory.
      - The port has been configured and compiled on WinXP SP3, Win98SE and
        MSDOS 6.22 and DOSLFN v0.41f.  There is absolute no guarantee that
        this may be possible with any other DOS-like OS.  Due to the use of
        long file names it will not be possible to configure and compile
        without LFN support.
      - The port does not support being compiled with assembler optimized
        code.
      - The reading/writing stream is switched into O_BINARY mode.  If the
        stream is connected to stdin/stdout/TTY, then Ctrl-C and Ctrl-Break
        are re-enabled so the user can interrupt the program.
      - This version of the port has been compiled using gcc346 and bnu2351b.

        As usual, all djgpp specific files (config.bat, diffs, readme files,
        etc.) are located in the djgpp subdir.

        For further information about LAME please read the info docs and NEWS file.


2.:     Installing the binary package.
        ==============================

2.1.:   Copy the binary distribution into the top DJGPP installation directory
        and unzip it running *ONE* of the following commands:
          unzip32 lme3100b.zip      or
          djtarx lme3100b.zip       or
          pkunzip -d lme3100b.zip


3.:     Building the binaries from sources.
        ===================================

3.1.:   Create a temporary directory and copy the source package into the
        directory.  If you download the source distribution from one of the
        DJGPP sites, just unzip it preserving the directory structure
        running *ONE* of the following commands:
          unzip32 lme3100s.zip      or
          djtarx lme3100s.zip       or
          pkunzip -d lme3100s.zip

3.2.:   To build the binaries you will need the following binary packages:
          djdev205.zip (or a later but NOT a prior version)
          bsh4253b.zip (or a later but NOT a prior version)
          gccNNNb.zip, bnuNNNb.zip, makNNNb.zip, filNNNb.zip, shlNNNb.zip,
          txtNNNb.zip, txiNNNb.zip, grepNNNb.zip, sedNNNb.zip, mktmpNNb.zip
          and difNNNb.zip.

        NNN represents the latest version number of the binary packages.  All
        this packages can be found in the /v2gnu directory of any
        ftp.delorie.com mirror.
        You will need bsh4253b.zip or later and *NOT* a prior version or
        the build will fail.  The same applies to djdev205.zip.

3.3.:   The package has been configured to be build in a separate build directory
        under the top srcdir (aka lame-3.100).  To build the binaries cd
        into "0build" directory.  If for some reason you want to reconfigure the
        package cd into the build directory and run the following commands:
          del config.cache
          make clean
          ..\djgpp\config ./..

        Please note that you _must_ delete the config.cache file in the "0build"
        directory or you will not really reconfigure the sources because the
        configuration informations will be read from the cache file instead
        of being newly computed.

        config.bat, among other things, will start the configure script passing
        to it a couple of arguments.  You can control these argument passing the
        following command line arguments to config.bat:
          cache or no-cache, default cache.  Cache in build directory.
          dep or no-dep, default no-dep.  No dependency tracking.
          silent or no-silent, default silent.  Controls the verbosity of the
                                                build process.
          asm or no-asm, default no-asm.  Disable the usage of optimized
                                          assembler code.

        To build the programs in a directory other than where the sources are,
        you must add the parameter that specifies the source directory,
        e.g:
          x:\src\contrib\lame-3.100\djgpp\config x:/src/contrib/lame-3.100

        Lets assume you want to build the binaries in a directory placed on a
        different drive (z:\build in this case) from where the sources are,
        then you will run the following commands:
          z:
          md \build
          cd \build
          x:\src\contrib\lame-3.100\djgpp\config x:/src/contrib/lame-3.100

        The order of the options and the srcdir option does not matter.  You
        _must_ use forward slashes to specify the source directory.

        The batch file will set same environment variables, make MSDOS specific
        modifications to the Makefile.in's and supply all other needed options
        to the configure script.

3.4.:   To compile the package run from the directory where you have configured
        the sources the command:
          make

3.5.:   To install the binary, info docs and man pages run the following command
        from the directory where you have configured the sources:
          make install

        This will install the products into your DJGPP installation tree given
        by the default prefix "/dev/env/DJDIR".  If you prefer to install them
        into some other directory you will have to set prefix to the appropriate
        value:
          make install prefix=z:/some/other/place



        Send LAME specific bug reports to
        <https://sourceforge.net/p/lame/mailman/lame-dev/>.
        Send suggestions and bug reports concerning the DJGPP port
        to comp.os.msdos.djgpp or <djgpp@delorie.com>.


Enjoy.

          Guerrero, Juan Manuel <juan.guerrero@gmx.de>
