Installation of the package:
During the installation the following rules apply:
The installation process:
Unfortunatly there is always a problem. Some systems don't have a full featured install other lack the -R switch on cp. There is a install program in the install subdirectory of the distribution. Use it if your's doesn't understand the -d switch. (This install also supports an environment variable INSTALLFILE, which can point to a file where a list of installed files is to be loged.)
Set the variable PARSEPROG to either ``sgmls'' or ``nsgmls''. Do not use a full path here!
Also decide whether to generate the LaTeX for the graphics package or the epsfig substyle. There is the variable GRPHPKG for. Set this to ``grphcs'' or to ``epsfig''. I don't know if epsfig works with LaTeX2e nor if graphics works with LaTeX 2.09. I recomented to use epsfig with version 2.09 and graphics with 2e.
If you need, adapt the variables holding the make, cp and mkdir program as well as the mkdir options used through the installation process.
There is still some support for the and the variable REMLOC left in. This is from the old version, may disappear some day and is no longer full supported. You can choose either local or remote (probably local). (The remote installation sets up a quite tricky environment, where some of the used commands are accessed on a remote host.)
You need to change the source back to the old module language of bigloo.
Within the module clauses (these is the first declaration within a file) of the files
are comments like
;BEGIN BIGLOO1.x ; ..... ;END BIGLOO1.x
Also further down within typeset.scm there is a block surounded with the same comments. It's a work around a bug within bigloo1.7.
Find these lines, remove the semicolons commenting out the lines between ``;BEGIN BIGLOO1.7'' and ``;END BIGLOO1.7'' respectivly comment out those line only for version 1.8.
Because these places may be different in your system, you might want to cd into the doc directory of the distribution. Do a ``make help'' to see what you can do. Then edit the Makefile to reflect your system and do a ``make doc'' to install the documentation. If you have trouble with the local handling of the notations you'll get some warnings.
(e.g., sdc -O ps -o targets.ps targets.sgml)
("SGML error at \\([, \t\n]+\\), line \\([0-9]+\\)" 1 2)
to get the goto-next-error funtions and the like in compile mode right. Uhm, for nsgmls you need a different pattern. But this should probably work out of the box.
I personally found the SGML-mode of emacs not suitable (these DTD's require to few markup to make this mode resonalble and the text formatting support was too limited for my taste). Therefor I (and others) hacked a slight modification. bin/mode.el holds the code for a new mode I like (especially for the folding properties). (Please note that this mode reflects personal taste.) It's far from perfect, especialy the highlighting is broken. Unfortunatly the 19.31 update broke the code. Users of older version might uncomment one line in the keymap to get the closing angle work again.
If you issue a ``make instbbset'' from the distribution directory you get it installed in $(prefix)/bin and the manpage in $prefix/man/man1.
sdc -O latex -o targets.tex doc/targets.sgml
Note, that you need to format the file doc/target.sgmlwhich includes the other doc/target.text.
In the case you encounter any problems or find bugs, typos etc. please
mail me: Joerg.Wittenberger@inf.tu-dresden.de.
D Changes
Because the old code is left in, some files are hardly clean and easy to read.