Implementation hints This version of EULER has been programmed on an IBM-RS6000 machine, with AIX 3.1.5 and XWindows X11 Release 3. To help you solve problems on other machines, follow these instructions. I have tested the program on Linux and Sun.
Memory EULER uses a fixed portion of memory, the size of which must be specified at program start. To do this use the "-s" command line option. The default value is contained in the variable memsize (1 MByte) of "sysdepx.c". Change this according to your needs and resources. Since UNIX uses demand paging, you may choose a high and sufficient value here.
Floating point allignment If your machine requires 8-Byte allignment, you should define SPECIAL_ALIGNMENT. This is necesssary for DEC and Sun architectures.
Floating point errors EULER catches floating point errors, when the makro FPE is defined. However, it is superior to use the IEEE standard floating point extensions INF and NaN. If you have these available, do not define FPE. Most machines do not have hardware infinity and need FPE. You will notice, if you need it, when Euler crashes after the command 1/0.
Fonts EULER uses two fonts, a text and a graphics font. These fonts can be chosen in the command line. The default fonts are set in the makefile by makro definitions. Change this to the needs of your XWindow version.
Timer EULER needs a timer for the wait function. If your machine is an RS6000, you can use its accurate timer function. If not, undefine the makro definition in the makefile. Then EULER will use standard UNIX time functions.
Colors EULER uses colors for graphics. You can set these colors in the command line by name. You can also change the default colors in the file "sysdepx.c".
Directories You should create directories euler/source and euler/progs in your home directory. All *.e files and euler.cfg should be in euler/progs. The source files should be in euler/source. You should make a shell script, which switches to the directory progs and then calls xeuler there.
Special care has to be taken on Sun based machines. First of all, you need an ANSI-C compiler. Most Gnu-C++ ports will suffice, but not all. If you have it, use acc. Then you will need to define the SUN macro in the makefile. This will make your keyboard work correctly.
The command line options accepted by EULER are
makein the source directory. This will create xeuler in source. You can test it by running xeuler. You may also create a non-graphics version with
make noxeulerThe command
make installthen copies xeuler and noxeuler to the progs directory. You should then create a shell script, which starts xeuler, in your $HOME/bin file, or you can start xeuler yourself in the progs directory. There should be a file euler.cfg, which loads the ../progs/util.e.
To create the documentation, start
make htmlThis will create several *.html files in the make directory, which you can read with your Web-Browser. If you want a printed documentation, start
make docYou can send the files docs/*.doc to your printer.
You should also issue the command
>load "demo"to get a good idea, what EULER can do for you.
Dr. R. Grothmann Kath. Univ. Eichstaett D-85071 Eichstaett Germany
To print the graphics you may use the standard harcopy commands of XWindows. However, I am using a self made xlaser command, which produces better output an a HP laserjet printer.
There are some command line options available.