This is a port of GNU Readline 7.0 to MSDOS/DJGPP.

The Readline library provides a set of functions for use by applications
that allow users to edit command lines as they are typed in.  Both
Emacs and vi editing modes are available.  The Readline library includes
additional functions to maintain a list of previously-entered command
lines, to recall and perhaps reedit those lines, and perform csh-like
history expansion on previous commands.


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

        - The port is based on the port of readline 2.2 and uses the termios
        emulation provided by it.  It has been slightly adjusted to work with
        DJGPP 2.05.  It also supports copying from Windows clipboard as the
        readline port from bash does if the rquired functions are provided by
        the used DOS version.  Most of the other changes are required to handle
        DOS specific slash and backslash issues and to pacify the compiler.

        - The port will check at run time if LFN support is available or not.
        If available, then it will look for ".inputrc" and ".history"  as
        configuration files.  If one of them is not available then it will try
        _inputrc" and/or "_history" as alternative file names.  This means that
        if LFN support is available, the POSIX file names will always be tried
        before the DOS file names are tried.  Of course, if only SFN support is
        available only the DOS versions of the file names will be tried.

        - The port will try to load the system wide configuration file using
        the file name "/dev/env/DJDIR/etc/inputrc" instead of the hard coded
        "/etc/inputrc".  The system wide INPUTRC file is always tried to be
        load if the loading of "~/.inputrc" fails and before "~/_inputrc" is
        tried to be load on LFN systems.

        - If pdcurses is installed it will be used to provide termios functionality
        instead of the one provided by the C-library.  If you prefer the termios
        functionality profided by the C-library you will have to uninstall pdcurses
        before you configure the sources.  The sources have been configured
        without pdcurses support.

        - The port has been configured and compiled on WinXP SP3.  There is 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.

        This version of the port has been compiled using gcc346 and bnu228b.

        As usual, all djgpp specific files (config.bat, diffs, README files,
        etc.) are stored in the /djgpp directory.

        For further information about GNU Readline 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,
        just unzip it preserving the directory structure running *ONE* of the
        following commands:
          unzip32 rdln70br2.zip      or
          djtarx rdln70br2.zip       or
          pkunzip -d rdln70br2.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 rdln70sr2.zip      or
          djtarx rdln70sr2.zip       or
          pkunzip -d rdln70sr2.zip

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

        If you want to configure and compile this packages with NLS support
        enabled you must install licvNNNb.zip, lunsNNNb.zip and gtxNNNNb.zip.

        If you want to run the check you will need also:
          difNNNb.zip and mktmpNNNb.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 bsh205bbr3.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 readline-7.0).  To build the binaries cd
        into /_build 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 /_build
        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:
          nls or no-nls, default nls.  NLS support enabled.
          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.
        All other configure specific options are not set by config.bat so their
        values are left as they are.  If no arguments are passed to config.bat
        then the default values are used.


        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\gnu\readline-7.0\djgpp\config x:/src/gnu/readline-7.0

        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\gnu\readline-7.0\djgpp\config x:/src/gnu/readline-7.0

        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.:   The package provides no test suite but you can check if the port works
        by compiling the sample programs in the /examples directory.

3.6.:   To install the binary, info docs and man pages run the following command
        from the top srcdir:
          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 GNU Readline specific bug reports to <bug-readline@gnu.org>.
        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>
