This file describes the steps need to be taken to compile this package
under the different environments.

Join IRIT mailing list:		gershon@cs.technion.ac.il
Mailing list:			irit-mail@cs.technion.ac.il
Bug reports:			irit-bugs@cs.technion.ac.il

-----------------------------------------------------------------------------

OS2
---

   Edit the file makeflag.os2 in the main directory.
Set all the variables to the correct path you would like the include
files/libraries/binaries to be installed to.
   Type 'make -f makefile.os2'. This should build the libraries
(misc/cagd/prsr/graf) following by all the tools including the solid
modeler itself - IRIT.

   Once everything built, change directory to the binaries directory. Edit
all *.cfg configuration files and follow the instructions in them to configure
the programs to your system.
   On line help is saved in irit.hlp and is copied to the binaries
directory. In the docs directories, the 'irit.tex' can be latex'ed and printed
to get a hardcopy manual for IRIT. Alternatively print 'irit.doc' which is
a similar but plain text file.

   Each of the subdirectories illustrt/filters/poly3d-r/poly3d-h has a
batch file called test-os2.cmd. Run them to test your new executables.
  Note you will need a gif viewer for poly3d-r images and that test-os2.cmd on
poly3d-h do require ???Drvs display device executable to display the hidden
line removed results.
On the IRIT subdirectory type 'irit demo.irt' to run a demo of IRIT.
There are quite a few other .irt files in that directory you may want to try.
Make sure the IRIT_PATH environment variable is properly set as well as
OS2IRIT and OS2IRIT_POS as described in the manual. You can run all
these tests by executing 'make -f makefile.os2 test' from the main directory.

   Things to watch for:

* all the makefiles in the subdirectories source makeflag.unx via the line
  'include ../makeflag.os2'. If your make support different include structure
  or does not support it at all, you will have to change it or manually
  substitute makeflag.unx content into the subdirectory makefiles.
* poly3d-r requires gif_lib (see below) to build, a library that is not
  provided with this package. You can ftp it separately (see below).
  The poly3d-r renderer renders into 8 bit GIF images and results are
  medium at best. Using the filter IRIT2RAY, use RAYSHADE which is far
  superior and recommended.

-----------------------------------------------------------------------------

UNIX
----
   Edit the file makeflag.unx in the main directory.
Set all the variables to the correct path you would like the include
files/libraries/binaries to be installed to. You will, at least, need to
set SRC_DIR.
  Select the correct compiler flags if your architecture exists there, by
typing 'make -f makefile.unx' to get a list of supported platforms.
Otherwise create a new entry in makeflag.unx flags for your system.
   Type 'make -f makefile.unx xxxx', where xxxx is your platform. This
should build the libraries (misc, cagd, prsr, etc.) following by all the
tools including the solid modeller itself - IRIT.

   Once everything built, change directory to the binaries directory. Edit
all *.cfg configuration files and follow the instructions in them to configure
the programs to your system.
   On line help is saved in irit.hlp and is copied to the binaries
directory. In the docs directories, the 'irit.tex' can be latex'ed and printed
to get a hardcopy manual for IRIT. Alternatively print 'irit.doc' which is
a similar but plain text file.

   Each of the subdirectories illustrt/filters/poly3d-r/poly3d-h has a batch
file called test-unx. Run them to test your new executables by doing
'csh test-unx'. Note you will need a gif viewer for poly3d-r images and that
test-unx on poly3d-h do require ???drvs display device executable to display
the hidden line removed results.
On the IRIT subdirectory type 'irit demo.irt' to run a demo of IRIT.
There are quite a few other .irt files in that directory you may want to try.
Make sure the IRIT_PATH and IRIT_DISPLAY environment variables are properly
set as described in the manual. You can run all these tests by executing
'make -f makefile.unx test' from the main directory. Optionally you might
need to set the environment of IRIT_SERVER_PORT and IRIT_SERVER_HOST.

   Things to watch for:

* all the makefiles in the subdirectories source makeflag.unx via the line
  'include ../makeflag.unx'. If your make support different include structure
  or does not support it at all, you will have to change it or manually
  substitute makeflag.unx content into the subdirectory makefiles.
* Your system must support either X11 or gl. Without graphics you would not
  be able to build the display devices.
* poly3d-r is NOT building under UNIX by default. This is because you need
  another library called gif_lib to link to, and which is not
  provided with this package. You can ftp it separately (see below).
  The poly3d-r renderer renders into 8 bit GIF images and results are
  medium at best. Using the filter IRIT2RAY, use RAYSHADE which is far
  superior and recommended.

-----------------------------------------------------------------------------

AmigaOS
-------

The Amiga port of IRIT 7.0 was tested using gcc 2.7.2.1. (It can also be
compiled with SAS/C version 6.57, but the resulting IRIT binary has problems.)

When running demo.irt, IRIT required about 10M of memory, so you may
need to install VMM before you can use IRIT.

Compiling:

You will need GNU make, as well as the programs sh, cp, mv, rm, and echo.  If
you want to add Utah RLE support to irender, you will need to install the URT
header files and libraries (source is available from ftp.cs.utah.edu).  If you
want to build the documentation from scratch, you will need to build irender
with Utah RLE support and to install the rletops and crop programs from the
Utah raster toolkit.

Compiling with gcc:

Edit makeflag.ami, and modify the following assignments:
SRC_DIR  = Put here the name of the top level IRIT directory.
CPUFLAGS = Add the appropriate options for your CPU type and preferred
	   math option.

Also modify the URT, URT_INC, URT_LIB, and URT_FLAGS definitions to indicate
whether you want Utah raster toolkit support or not, and where the URT
libraries and header files are installed.

Type make -f makefile.ami at the top directory, and go for a cup of coffee.
When you return, all the binaries will be in the bin subdirectory.

Compiling with SAS/C:
(Currently not recommended--the resulting IRIT binary has problems.)

Edit makeflag.sas, and modify the following assignments:
SRC_DIR	= Put the name of the top level IRIT directory.
CFLAGS	= Modify the CPU= and MATH= options according to what CPU you
	  have and what kind of floating point math you want to use.
MATHLIB = Put the name of the math library with which you want to link.

Also modify the URT, URT_INC, URT_LIB, and URT_FLAGS definitions to indicate
whether you want Utah raster toolkit support or not, and where the URT
libraries and header files are installed.

Type make -f makefile.sas at the top directory, and go for a cup of coffee.
When you return, all the binaries will be in the bin subdirectory.

Differences between UNIX and Amiga IRIT:

None to speak of. There is no IRIT_SERVER_HOST environment variable, and
IRIT_SERVER_PORT points to the name of an Exec port rather than to
whatever it is that it points to in UNIX.  When amidrvs is displaying an
animation, the "Animate" button turns into a "Stop Anim" button; hit it
to stop the animation.  If you run amidrvs by hand, be sure to run it
after IRIT starts looking for it. Yes, I know that the synchronization
code between IRIT and amidrvs is an awful kludge, but since it works,
I'm in no particular hurry to fix it.

Bugs:
Quitting from amidrvs while IRIT is running, will cause IRIT to hang.

Bug reports:
If you think you've found a bug in the Amiga port (as opposed to a bug
in IRIT itself), send mail to kyrimis@cti.gr.

-----------------------------------------------------------------------------

WINDOWS NT
----------

   Edit the file makeflag.wnt in the main directory.
Set all the variables to the correct path you would like the include
files/libraries/binaries to be installed to.
   Type 'nmake -f makefile.wnt' (nmake is Microsoft's make provided with
the SDK of Window NT 3.1). This should build the libraries
(misc/cagd/prsr/graf) following by all the tools including the solid
modeler itself - IRIT.

   Once everything built, change directory to the binaries directory. Edit
all *.cfg configuration files and follow the instructions in them to configure
the programs to your system.
   On line help is saved in irit.hlp and is copied to the binaries
directory. In the docs directories, the 'irit.tex' can be latex'ed and printed
to get a hardcopy manual for IRIT. Alternatively print 'irit.doc' which is
a similar but plain text file.

   Each of the subdirectories illustrt/filters/poly3d-r/poly3d-h has a batch
file called test-os2.cmd. Run them to test your new executables.
   Note you will need a gif viewer for poly3d-r images and that test-os2.cmd on
poly3d-h do require ???drvs display device executable to display the hidden
line removed results.
On the IRIT subdirectory type 'irit demo.irt' to run a demo of IRIT.
There are quite a few other .irt files in that directory you may want to try.
Make sure the IRIT_PATH environment variable is properly set as well as
IRIT_DISPLAY. Optional are IRIT_SERVER_HOST and IRIT_SERVER_PORT as described
in the manual.
You can run all these tests by executing 'make -f makefile.os2 test' from
the main directory.

   Things to watch for:

* all the makefiles in the subdirectories source makeflag.unx via the line
  'include ../makeflag.os2'. If your make support different include structure
  or does not support it at all, you will have to change it or manually
  substitute makeflag.unx content into the subdirectory makefiles.
* poly3d-r requires gif_lib (see below) to build, a library that is not
  provided with this package. You can ftp it separately (see below).
  The poly3d-r renderer renders into 8 bit GIF images and results are
  medium at best. Using the filter IRIT2RAY, use RAYSHADE which is far
  superior and recommended.

-----------------------------------------------------------------------------

The intr_lib sources can be ftped from the following two places:

1. wuarchive.wustl.edu. directory mirrors/msdos/irit/intrlib?.zip
2. simtel20.arpa.mil, directory PD:<MSDOS.IRIT> as intrlib?.zip
where ? is the current version.

libintr.a (DJGPP) and intr_lib.lib (MSDOS) are built from this package.

-----------------------------------------------------------------------------

The gif_lib sources can be ftped from the following two places:

1. wuarchive.wustl.edu. directory mirrors/msdos/gif/giflib??.zip
2. simtel20.arpa.mil, directory PD:<MSDOS.GIF> as giflib??.zip
where ?? is the current version.

libgif.a (UNIX) and gif_libl.lib (MSDOS) are built from the lib subdirectory
of giflib??.zip package.

