This file gives information regarding cvs snapshots of flex. cvs
snapshots of flex contain the files which are under version control by
the flex maintainers for the flex project. These snapshots can be
found at:

ftp://ftp.uncg.edu/people/wlestes/

If you are not interested in flex development or you are not in need
of the latest bleeding-edge features, then cvs snapshots of flex are
not for you.

When you get a distribution of flex, a large number of intermediate
files needed to make building flex easy are included. You don't have
that in a cvs snapshot.

You will need various external tools in order to build the distribution. Here is
a (possibly incomplete) list of the required tools. Always get the latest
version of each tool; we list the versions used in development of
flex, but the listed versions may not work for you.

compiler suite;  e.g., gcc
bash or some other fairly robust sh-style shell
GNU bison;  to generate parse.c from parse.y
GNU m4 1.4; required by BNU autoconf (yes, it *must* be GNU m4)
GNU autoconf 2.54 and GNU automake 1.7; for generating Makefiles etc.
GNU gettext 0.11.5; for i18n
flex (latest beta release);  for bootstrap of scan.l
help2man 1.27; to generate man page
tar, gzip, etc.; for packaging of the source distribution
GNU texinfo 4.3d;  to build and test the flex manual
perl; GNU automake and GNU autoconf now depend on perl to run
GNU indent 2.8; for indenting the flex source the way we want it done

ONce you have all the necessary tools installed, life becomes
simple. To prepare the flex tree for building, run the script:

$ ./autogen.sh

in the top level of the flex source tree.
This script calls the various tools needed to get flex ready for the
GNU-style configure script to be able to work.

From this point on, building flex follows the usual configure, make,
make install routine, almost. When configuring the flex tree, pass the
--enable-maintainer-mode option to configure. If you forget, you will
see errors about a missing file `version.texi'.