This installation procedure sets up a GNU Cygwin environment which allows you to work in a UNIX like environment under Windows. It has been tested in Windows 95, 98, and 2000 machines. It is assumed you are somewhat familiar with some UNIX utilities. The advanced can install David Fiddes' GCC installation instead of the Motorobots.
This works for me, but be sure to understand any differences in you MRM or computer setup, as it could affect the operation. I've been pretty fortunate not to trash the CPU32BUG monitor (or MRM itself) yet.
NOTE: I hear, you don't actually need the cygwin installation as the motorobots installation package should contain everything, but I haven't tested that.
This installation covers a windows installation. A linux installation should be quite similar. assuming you are starting with a fresh windows machine the following should work for you:
Currently, the libraries do not come with the installation package and will need to be recompiled. To accomplish
this requires configuring the makefile variables to your particular installation. Currently, for the Windows (DOS)
environment, there is a top level makeinclude.dos that is used for each makefile.
I am currently using FLTK version 1.1.7, if your's is different, then you will need to set
the variable VERSION in the oomrm/makeinclude.dos to make the library. This should be set to the
version of the FLTK library you are compiling with. For example, for fltk-1.1.4, use VERSION="1.1.4".
NOTE: In Windows, I used to add each file to the archive after each compilation, but this turns out to increase the total
compile time from 5 min. to about 35 minutes. Now, after compiling for dos, type ./arit which recursively
adds all objects to their respective libraries. Believe it or not, it makes it much quicker.
Afterwards, move to the host directory and type 'doit' to create sim.exe.
NOTE: you cannot easily mix the host and 68332 compiles. To compile for the 68332 afterward, you must first remove all of the host object files (or do a make clean).
For the host installation, you will also require the graphics library-FLTK. For a cygwin installation, use the following instructions (others will be similar):
NOTE: The below is usually only necessary for gcc less than 3.0.   I now use gcc 3.3.1 with FLTK-1.1.7 and you can simply use the
./configure --enable-cygwin setup, and type "make" afterwards..
Just a matter of putting the const in.
The code documentation is not provided with the library and will need to be built with
Doxygen.
The easiest way after installing Doxygen, is to use the doxywizard that comes with the application and
load and run the files "abstract.doxygen" and "hardware.doxygen" in the "oomrm" root directory. You may need to tailor the output/input directories
to suit your installation; after customizing, select run and the documentation should get built.
The system now has online help, but first the environmental variable OOMRM_HELP must first be exported to the
oomrm/doc directory. For example, export OOMRM_HELP="c:/cygwin/home/derek/oomrm/doc/" (final slash required).
This can either be exported manually or put in your login profile (see myenv in the oomrm root directory) or on Windows
you can add them to the user's environemental variables through the "My Computer" icon for the more advanced.
FLTK
// HP-UX, Cygwin define the comparison function like this:
return scandir(d, list, 0, (int(*)(dirent **, dirent **))sort);
To:
// HP-UX, Cygwin define the comparison function like this:
return scandir(d, list, 0, (int(*)(const dirent **, const dirent **))sort);
C/C++ Code Documentation (Doxygen)
In-Line Help
Users Guide Generation
The PDF guide also does not come with the default installation package. Either download it seperately or
remake it using the oomrm.book setup file with the HTWLDOC application.