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/iritfltr/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. Select the correct compiler flags if your architecture exists there. Otherwise create a new entry for these flags for your system. Type 'make -f makefile.unx'. 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/iritfltr/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 most of the tools, including IRIT itself. * 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. ----------------------------------------------------------------------------- AMIGADOS -------- The Amiga port of Irit requires SAS/C or gcc, versions 6.3 and 2.4.5 or later, respectively. Do not use the optimizer with either compiler. Building with SAS/C: Edit makeflag.sas, and modify the following assignments: SRC_DIR = Put here the name of the top level irit directory. DFLAGS = Modify the DEFINE=M68881 directive according to what kind of floating point math you want. Use DEFINE=M68881 if you have an FPU (68881/68882/68040), DEFINE=MIEEE if you want to use the IEEE math libraries, or MFFP if you want to use Motorolla fast floating point math. (I've no idea if this last one will work!) This definition controls which of the three include files, , or will be included after . CFLAGS = Modify the CPU= and MATH= options according to what CPU you have and what kind of floating point math you want to use. Do not be tempted to add the OPTIMIZE flag here. (You're going to hate me for this!) Since smake does not have an include directive, you'll now have to edit makefile.sas in the top level directory and in all subdirectories. Delete all lines between #-----'s and replace them with the contents of makeflag.sas. Alternatively, you can make the above changes in each makefile.sas. Assuming you're still with me, type smake -f makefile.sas at the top directory, and go for a very large cup of coffee. When you return, all the binaries will be in the bin subdirectory. Building with gcc: Proceed as above, with the following differences: The make flags are in makeflag.ami, and the makefiles are called makefile.ami. There are no DFLAGS to change, and in CFLAGS change the -m68040 and -m68881 options to reflect your CPU and preferred floating point math type. After updating all makefiles (if you have a make with an include directive this updating should be much simpler), type make -f makefile.ami and take an even longer coffee break. 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. If amidrvs is in your path, you do not have to set IRIT_DISPLAY, as irit will use "amidrvs -s-" by default. If for some reason you have to/ want to 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@theseas.ntua.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' (namke 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/iritfltr/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: 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: 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.