URL
                    https://opencores.org/ocsvn/openrisc_me/openrisc_me/trunk
                
            Subversion Repositories openrisc_me
[/] [openrisc/] [trunk/] [gnu-src/] [gdb-6.8/] [readline/] [README] - Rev 294
Go to most recent revision | Compare with Previous | Blame | View Log
Introduction============This is the Gnu Readline library, version 5.1.The Readline library provides a set of functions for use by applicationsthat allow users to edit command lines as they are typed in. BothEmacs and vi editing modes are available. The Readline library includesadditional functions to maintain a list of previously-entered commandlines, to recall and perhaps reedit those lines, and perform csh-likehistory expansion on previous commands.The history facilites are also placed into a separate library, theHistory library, as part of the build process. The History librarymay be used without Readline in applications which desire itscapabilities.The Readline library is free software, distributed under the terms ofthe [GNU] General Public License, version 2. For more information, seethe file COPYING.To build the library, try typing `./configure', then `make'. Theconfiguration process is automated, so no further intervention shouldbe necessary. Readline builds with `gcc' by default if it isavailable. If you want to use `cc' instead, typeCC=cc ./configureif you are using a Bourne-style shell. If you are not, the followingmay work:env CC=cc ./configureRead the file INSTALL in this directory for more information about howto customize and control the build process.The file rlconf.h contains C preprocessor defines that enable and disablecertain Readline features.The special make target `everything' will build the static and sharedlibraries (if the target platform supports them) and the examples.Examples========There are several example programs that use Readline features in theexamples directory. The `rl' program is of particular interest. Itis a command-line interface to Readline, suitable for use in shellscripts in place of `read'.Shared Libraries================There is skeletal support for building shared versions of theReadline and History libraries. The configure script createsa Makefile in the `shlib' subdirectory, and typing `make shared'will cause shared versions of the Readline and History librariesto be built on supported platforms.If `configure' is given the `--enable-shared' option, it will attemptto build the shared libraries by default on supported platforms.Configure calls the script support/shobj-conf to test whether ornot shared library creation is supported and to generate the valuesof variables that are substituted into shlib/Makefile. If youtry to build shared libraries on an unsupported platform, `make'will display a message asking you to update support/shobj-conf foryour platform.If you need to update support/shobj-conf, you will need to createa `stanza' for your operating system and compiler. The script usesthe value of host_os and ${CC} as determined by configure. Forinstance, FreeBSD 4.2 with any version of gcc is identified as`freebsd4.2-gcc*'.In the stanza for your operating system-compiler pair, you will need todefine several variables. They are:SHOBJ_CC The C compiler used to compile source files into shareableobject files. This is normally set to the value of ${CC}by configure, and should not need to be changed.SHOBJ_CFLAGS Flags to pass to the C compiler ($SHOBJ_CC) to createposition-independent code. If you are using gcc, thisshould probably be set to `-fpic'.SHOBJ_LD The link editor to be used to create the shared library fromthe object files created by $SHOBJ_CC. If you are usinggcc, a value of `gcc' will probably work.SHOBJ_LDFLAGS Flags to pass to SHOBJ_LD to enable shared object creation.If you are using gcc, `-shared' may be all that is necessary.These should be the flags needed for generic shared objectcreation.SHLIB_XLDFLAGS Additional flags to pass to SHOBJ_LD for shared librarycreation. Many systems use the -R option to the linkeditor to embed a path within the library for run-timelibrary searches. A reasonable value for such systems wouldbe `-R$(libdir)'.SHLIB_LIBS Any additional libraries that shared libraries should belinked against when they are created.SHLIB_LIBPREF The prefix to use when generating the filename of the sharedlibrary. The default is `lib'; Cygwin uses `cyg'.SHLIB_LIBSUFF The suffix to add to `libreadline' and `libhistory' whengenerating the filename of the shared library. Many systemsuse `so'; HP-UX uses `sl'.SHLIB_LIBVERSION The string to append to the filename to indicate the versionof the shared library. It should begin with $(SHLIB_LIBSUFF),and possibly include version information that allows therun-time loader to load the version of the shared libraryappropriate for a particular program. Systems using sharedlibraries similar to SunOS 4.x use major and minor libraryversion numbers; for those systems a value of`$(SHLIB_LIBSUFF).$(SHLIB_MAJOR)$(SHLIB_MINOR)' is appropriate.Systems based on System V Release 4 don't use minor versionnumbers; use `$(SHLIB_LIBSUFF).$(SHLIB_MAJOR)' on those systems.Other Unix versions use different schemes.SHLIB_DLLVERSION The version number for shared libraries that determines APIcompatibility between readline versions and the underlyingsystem. Used only on Cygwin. Defaults to $SHLIB_MAJOR, butcan be overridden at configuration time by defining DLLVERSIONin the environment.SHLIB_DOT The character used to separate the name of the shared libraryfrom the suffix and version information. The default is `.';systems like Cygwin which don't separate version informationfrom the library name should set this to the empty string.SHLIB_STATUS Set this to `supported' when you have defined the othernecessary variables. Make uses this to determine whetheror not shared library creation should be attempted.You should look at the existing stanzas in support/shobj-conf for ideas.Once you have updated support/shobj-conf, re-run configure and type`make shared'. The shared libraries will be created in the shlibsubdirectory.If shared libraries are created, `make install' will install them.You may install only the shared libraries by running `makeinstall-shared' from the top-level build directory. Running `makeinstall' in the shlib subdirectory will also work. If you don't wantto install any created shared libraries, run `make install-static'.Documentation=============The documentation for the Readline and History libraries appears inthe `doc' subdirectory. There are three texinfo files and aUnix-style manual page describing the facilities available in theReadline library. The texinfo files include both user andprogrammer's manuals. HTML versions of the manuals appear in the`doc' subdirectory as well.Reporting Bugs==============Bug reports for Readline should be sent to:bug-readline@gnu.orgWhen reporting a bug, please include the following information:* the version number and release status of Readline (e.g., 4.2-release)* the machine and OS that it is running on* a list of the compilation flags or the contents of `config.h', ifappropriate* a description of the bug* a recipe for recreating the bug reliably* a fix for the bug if you have one!If you would like to contact the Readline maintainer directly, send mailto bash-maintainers@gnu.org.Since Readline is developed along with bash, the bug-bash@gnu.org mailinglist (mirrored to the Usenet newsgroup gnu.bash.bug) often containsReadline bug reports and fixes.Chet Rameychet@po.cwru.edu
Go to most recent revision | Compare with Previous | Blame | View Log

