Home | History | Annotate | only in /sfw/usr/src/cmd/gnu-gperf/gperf-3.0.3
Up to higher level directory
NameDateSize
aclocal.m429-Aug-20052.3K
AUTHORS25-Nov-200280
ChangeLog30-Apr-2007146.8K
configure04-Apr-200777.1K
configure.ac05-Apr-20071.5K
COPYING14-May-200517.7K
doc/02-May-2007
INSTALL04-Apr-20077.6K
lib/02-May-2007
Makefile.devel04-Apr-20071.2K
Makefile.in14-May-20051.7K
Makefile.msvc14-May-20055.9K
Makefile.vms14-May-20056.2K
mkinstalldirs20-Aug-2000722
NEWS31-Mar-20073.1K
README02-Aug-20011.2K
README.vms05-May-2003139
README.woe3222-Aug-20041.3K
src/02-May-2007
tests/02-May-2007

README

      1 This is GNU gperf. It is a program that generates perfect hash
      2 functions for sets of key words.  A perfect hash function is:
      3 
      4           A hash function and a data structure that allows 
      5           recognition of a key word in a set of words using 
      6           exactly 1 probe into the data structure.
      7 
      8 The doc/gperf.html file explains how the program works, the form of
      9 the input, what options are available, and hints on choosing the best
     10 options for particular key words set.
     11 
     12 See the file NEWS for a list of major changes in the current release.
     13 
     14 See the file INSTALL for compilation and installation instructions.
     15 
     16 Output from the GPERF program is used to recognize reserved words in
     17 the GNU C, GNU C++, and GNU Pascal compilers, as well as with the GNU
     18 indent program.
     19 
     20 For general documentation on the coding and usage standards
     21 this distribution follows, see the GNU standards document
     22 ftp://ftp.gnu.org/pub/gnu/standards.*, especially the 'Makefile
     23 Conventions', 'Configuration', and 'User Interfaces' sections.
     24 
     25 Mail suggestions and bug reports to <bug-gnu-gperf (a] gnu.org>.  When
     26 reporting bugs, please include in the subject line the package name
     27 and version (output of 'gperf --version') for which you found a problem.
     28 
     29

README.vms

      1 Installation on VMS:
      2 
      3 - Build instructions:
      4 
      5   $ mms /description=Makefile.vms
      6 
      7 - Installation:
      8 
      9   $ mms /description=Makefile.vms install
     10

README.woe32

      1 Installation on Woe32 (WinNT/2000/XP, Win95/98/ME):
      2 
      3 - Requires MS Visual C/C++ 4.0 or 5.0 or 6.0 or 7.0.
      4 
      5   Note that binaries created with MSVC 7.0 should not be distributed: They
      6   depend on a closed-source library 'msvcr70.dll' which is not normally part
      7   of a Woe32 installation. You cannot distribute 'msvcr70.dll' with the
      8   binaries - this would be a violation of the GPL and of the Microsoft EULA.
      9   You can distribute the binaries without including 'msvcr70.dll', but this
     10   will cause problems for users that don't have this library on their system.
     11   Therefore it is not recommended. This problem does not occur with MSVC 6.0
     12   and earlier.
     13 
     14 - Cannot build in a separate directory.
     15 
     16 - Build instructions:
     17 
     18    Make sure that the MSVC4.0 or MSVC5.0 or MSVC6.0 or MSVC7.0 utilities
     19    ("cl" etc.) are found in PATH. In a typical MSVC6.0 installation, this
     20    can be achieved by running
     21         C:\Program Files\Microsoft Visual Studio\VC98\bin\vcvars32.bat
     22    In a typical MSVC7.0 installation, it can be achieved by running
     23         C:\Program Files\Microsoft Visual Studio .NET\Common7\Tools\vsvars32.bat
     24 
     25         nmake -f Makefile.msvc
     26 
     27 - Installation:
     28 
     29    Either:
     30 
     31         Copy gperf.exe to your program repository.
     32 
     33    Or:
     34 
     35         nmake -f Makefile.msvc install prefix=InstallBaseDirectory
     36