Initial revision

INSTALL

@@ -0,0 +1,146 @@
+ This is a generic INSTALL file for utilities distributions.
+If this package does not come with, e.g., installable documentation or
+data files, please ignore the references to them below.
+
+ The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation, and
+creates the Makefile(s) (one in each subdirectory of the source
+directory). In some packages it creates a C header file containing
+system-dependent definitions. It also creates a file `config.status'
+that you can run in the future to recreate the current configuration.
+
+To compile this package:
+
+1. Configure the package for your system.
+
+ Normally, you just `cd' to the directory containing the package's
+source code and type `./configure'. If you're using `csh' on an old
+version of System V, you might need to type `sh configure' instead to
+prevent `csh' from trying to execute `configure' itself.
+
+ Running `configure' takes awhile. While it is running, it
+prints some messages that tell what it is doing. If you don't want to
+see any messages, run `configure' with its standard output redirected
+to `/dev/null'; for example, `./configure >/dev/null'.
+
+ To compile the package in a different directory from the one
+containing the source code, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'. `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script. `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'. If
+for some reason `configure' is not in the source code directory that
+you are configuring, then it will report that it can't find the source
+code. In that case, run `configure' with the option `--srcdir=DIR',
+where DIR is the directory that contains the source code.
+
+ By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc. You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'. Alternately, you can do so by consistently
+giving a value for the `prefix' variable when you run `make', e.g.,
+ make prefix=/usr/gnu
+ make prefix=/usr/gnu install
+
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+give `configure' the option `--exec-prefix=PATH' or set the `make'
+variable `exec_prefix' to PATH, the package will use PATH as the prefix
+for installing programs and libraries. Data files and documentation
+will still use the regular prefix. Normally, all files are installed
+using the same prefix.
+
+ Some packages pay attention to `--with-PACKAGE' options to
+`configure', where PACKAGE is something like `gnu-as' or `x' (for the
+X Window System). They may also pay attention to `--enable-FEATURE'
+options, where FEATURE indicates an optional part of the package. The
+README should mention any `--with-' and `--enable-' options that the
+package recognizes.
+
+ `configure' also recognizes the following options:
+
+`--help'
+ Print a summary of the options to `configure', and exit.
+
+`--quiet'
+`--silent'
+ Do not print messages saying which checks are being made.
+
+`--verbose'
+ Print the results of the checks.
+
+`--version'
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+
+`--x-includes=DIR'
+ X include files are in DIR.
+
+`--x-libraries=DIR'
+ X library files are in DIR.
+
+ `configure' also accepts and ignores some other options.
+
+ On systems that require unusual options for compilation or linking
+that the package's `configure' script does not know about, you can give
+`configure' initial values for variables by setting them in the
+environment. In Bourne-compatible shells, you can do that on the
+command line like this:
+
+ CC='gcc -traditional' LIBS=-lposix ./configure
+
+On systems that have the `env' program, you can do it like this:
+
+ env CC='gcc -traditional' LIBS=-lposix ./configure
+
+ Here are the `make' variables that you might want to override with
+environment variables when running `configure'.
+
+ For these variables, any value given in the environment overrides the
+value that `configure' would choose:
+
+ - Variable: CC
+ C compiler program. The default is `cc'.
+
+ - Variable: INSTALL
+ Program to use to install files. The default is `install' if you
+ have it, `cp' otherwise.
+
+ For these variables, any value given in the environment is added to
+the value that `configure' chooses:
+
+ - Variable: DEFS
+ Configuration options, in the form `-Dfoo -Dbar...'. Do not use
+ this variable in packages that create a configuration header file.
+
+ - Variable: LIBS
+ Libraries to link with, in the form `-lfoo -lbar...'.
+
+ If you need to do unusual things to compile the package, we encourage
+you to figure out how `configure' could check whether to do them, and
+mail diffs or instructions to the address given in the README so we
+can include them in the next release.
+
+2. Type `make' to compile the package. If you want, you can override
+the `make' variables CFLAGS and LDFLAGS like this:
+
+ make CFLAGS=-O2 LDFLAGS=-s
+
+3. If the package comes with self-tests and you want to run them,
+type `make check'. If you're not sure whether there are any, try it;
+if `make' responds with something like
+ make: *** No way to make target `check'. Stop.
+then the package does not come with self-tests.
+
+4. Type `make install' to install programs, data files, and
+documentation.
+
+5. You can remove the program binaries and object files from the
+source directory by typing `make clean'. To also remove the
+Makefile(s), the header file containing system-dependent definitions
+(if the package uses one), and `config.status' (all the files that
+`configure' created), type `make distclean'.
+
+ The file `configure.in' is used to create `configure' by a program
+called `autoconf'. You only need it if you want to regenerate
+`configure' using a newer version of `autoconf'.

Makefile.dsu

@@ -0,0 +1,50 @@
+# Makefile for less.
+# MS-DOS version
+
+#### Start of system configuration section. ####
+
+CC = cl
+LIBDIR = \msc6.0\lib
+
+CFLAGS = -O /Alfw
+LDFLAGS = -O
+LIBS = ${LIBDIR}\llibce.lib ${LIBDIR}\graphics.lib
+
+#### End of system configuration section. ####
+
+# This rule allows us to supply the necessary -D options
+# in addition to whatever the user asks for.
+.c.obj:
+ ${CC} -c -I. ${CPPFLAGS} ${CFLAGS} $<
+
+SRC = main.c doscreen.c brac.c ch.c charset.c cmdbuf.c command.c \
+ decode.c edit.c filename.c forwback.c help.c ifile.c \
+ input.c jump.c line.c linenum.c lsystem.c \
+ mark.c optfunc.c option.c opttbl.c os.c output.c \
+ position.c prompt.c search.c signal.c tags.c \
+ ttyin.c version.c
+OBJ = main.obj doscreen.obj brac.obj ch.obj charset.obj cmdbuf.obj command.obj \
+ decode.obj edit.obj filename.obj forwback.obj help.obj ifile.obj \
+ input.obj jump.obj line.obj linenum.obj lsystem.obj \
+ mark.obj optfunc.obj option.obj opttbl.obj os.obj output.obj \
+ position.obj prompt.obj search.obj signal.obj tags.obj \
+ ttyin.obj version.obj
+
+all: less lesskey
+
+# This is really horrible, but the command line is too long for 
+# MS-DOS if we try to link $(OBJ).
+less: $(OBJ)
+ -del lesskey.obj
+ $(CC) $(LDFLAGS) -o $@ *.obj $(LIBS)
+
+lesskey: lesskey.obj
+ $(CC) $(LDFLAGS) -o $@ lesskey.obj $(LIBS)
+
+$(OBJ): less.h defines.h
+
+clean:
+ -del *.obj 
+ -del less.exe
+ -del lesskey.exe
+

Makefile.in

@@ -0,0 +1,136 @@
+# Makefile for less.
+
+#### Start of system configuration section. ####
+
+srcdir = @srcdir@
+VPATH = @srcdir@
+
+CC = @CC@
+INSTALL = @INSTALL@
+INSTALL_PROGRAM = @INSTALL_PROGRAM@
+INSTALL_DATA = @INSTALL_DATA@
+
+CFLAGS = -O
+CFLAGS_COMPILE_ONLY = -c
+LDFLAGS = 
+O=o
+
+LIBS = @LIBS@
+
+prefix = /usr/local
+exec_prefix = $(prefix)
+
+# Where the installed binary goes.
+bindir = $(exec_prefix)/bin
+binprefix = 
+
+# Where the help file goes.
+datadir = $(prefix)/lib
+
+mandir = $(prefix)/man/man$(manext)
+manext = 1
+manprefix = 
+
+#### End of system configuration section. ####
+
+SHELL = /bin/sh
+
+# This rule allows us to supply the necessary -D options
+# in addition to whatever the user asks for.
+.c.o:
+ $(CC) -I. $(CFLAGS_COMPILE_ONLY) $(CPPFLAGS) $(CFLAGS) $<
+
+SRC = main.c screen.c brac.c ch.c charset.c cmdbuf.c \
+ command.c decode.c edit.c filename.c forwback.c \
+ help.c ifile.c input.c jump.c line.c linenum.c \
+ lsystem.c mark.c optfunc.c option.c opttbl.c os.c \
+ output.c position.c prompt.c search.c signal.c \
+ tags.c ttyin.c version.c 
+OBJ = main.$(O) screen.$(O) brac.$(O) ch.$(O) charset.$(O) cmdbuf.$(O) \
+ command.$(O) decode.$(O) edit.$(O) filename.$(O) forwback.$(O) \
+ help.$(O) ifile.$(O) input.$(O) jump.$(O) line.$(O) linenum.$(O) \
+ lsystem.$(O) mark.$(O) optfunc.$(O) option.$(O) opttbl.$(O) os.$(O) \
+ output.$(O) position.$(O) prompt.$(O) search.$(O) signal.$(O) \
+ tags.$(O) ttyin.$(O) version.$(O) @REGEX_O@
+DISTFILES = ${SRC} regexp.c regexp.h \
+ INSTALL Makefile.in Makefile.dos README NEWS \
+ configure configure.in doscreen.c acconfig.h lesskey.c \
+ cmd.h defines.dos funcs.h less.h option.h position.h \
+ install.sh defines.h.in defines.h.top mkinstalldirs \
+ less.nro lesskey.nro less.man lesskey.man less.hlp 
+
+all: less lesskey
+
+less: $(OBJ)
+ $(CC) $(LDFLAGS) -o $@ $(OBJ) $(LIBS)
+
+lesskey: lesskey.$(O)
+ $(CC) $(LDFLAGS) -o $@ lesskey.$(O)
+
+$(OBJ): less.h defines.h funcs.h
+
+filename.$(O): filename.c
+ ${CC} -c -DHELPFILE=\"${datadir}/less.hlp\" -I. ${CPPFLAGS} ${CFLAGS} ${srcdir}/filename.c
+
+install: all less.hlp less.nro installdirs
+ ${INSTALL_PROGRAM} less ${bindir}/${binprefix}less
+ ${INSTALL_PROGRAM} lesskey ${bindir}/${binprefix}lesskey
+ ${INSTALL_DATA} ${srcdir}/less.hlp ${datadir}/less.hlp
+ ${INSTALL_DATA} ${srcdir}/less.nro ${mandir}/${manprefix}less.${manext}
+ ${INSTALL_DATA} ${srcdir}/lesskey.nro ${mandir}/${manprefix}lesskey.${manext}
+
+installdirs: mkinstalldirs
+ ${srcdir}/mkinstalldirs ${bindir} ${datadir} ${mandir}
+
+uninstall:
+ rm -f ${bindir}/${binprefix}less ${bindir}/${binprefix}lesskey
+ rm -f ${datadir}/less.hlp
+ rm -f ${mandir}/less.${manext} ${mandir}/lesskey.${manext}
+
+info:
+install-info:
+dvi:
+check:
+installcheck:
+
+TAGS:
+ cd ${srcdir} && etags *.c *.h
+
+# config.status might not change defines.h
+# Don't rerun config.status if we just configured (so there's no stamp-h).
+defines.h: stamp-h
+stamp-h: defines.h.in config.status
+ test ! -f stamp-h || ./config.status
+ touch stamp-h
+Makefile: Makefile.in config.status
+ ./config.status
+config.status: configure
+ ./config.status --recheck
+
+lint:
+ lint -I. $(CPPFLAGS) $(SRC)
+newfuncs:
+ awk -f mkfuncs.awk $(SRC) >newfuncs
+clean:
+ rm -f *.$(O) core less lesskey
+
+mostlyclean: clean
+
+distclean: clean
+ rm -f Makefile config.status defines.h stamp-h
+
+realclean: distclean
+ rm -f TAGS
+
+dist: ${DISTFILES}
+ if [ ! -d release ]; then mkdir release; fi
+ @REL=`sed -e '/char version/!d' -e 's/[^0-9.]*\([0-9.]*\).*/less-\1/' -e q version.c`; \
+ rm -rf release/$$REL; mkdir release/$$REL; \
+ echo "Creating release/$$REL/$$REL.tar.gz"; \
+ rm -rf $$REL; mkdir $$REL; \
+ for file in ${DISTFILES}; do \
+ ln $$file $$REL || \
+ { echo "cannot link, copying $$file"; cp -p $$file $$REL; }; \
+ done; \
+ tar -chf - $$REL | gzip -c >release/$$REL/$$REL.tar.gz; \
+ rm -rf $$REL