`grog' and `groffer' (maybe something else in the future) need the information of the options used by `groff'.
I wrote a Perl program `read_groff_options.pl' being stored in `<groff_top_dir>/src/roff/groff'. In this directory there is also the file `groff.cpp'. The Perl program reads from `groff.cpp' the function `synopsis' that contains information of the `groff' options. From this there information, a 2-liner is created and written to STDOUT. The actual output reads: noarg: abceghijklpstvzCENRSUVXZ witharg: FmTfwWMdrnoPDKLI That information can easily used by Perl. So `grog' and `groffer' can run `read_groff_options.pl' before the run of `make' and process its output. By the run of `make', `read_groff_options.pl' is run and its output is stored into the file `groff_options.info'. By `make install', this output file isx stored in the `groff libdir'. After the `make' installation, this output file can be used by `grog' and `groffer' without using `read_groff_options.pl'. Is there any trouble with this concept? Bernd Warken
