Building

Building the system is pretty strait forward. Exopc uses gmake and you should be able to go into a directory and type ``gmake'' either by itself or with the targets ``install'' or ``clean''. ``clean'' does the normal thing while ``install'' copies files from the build area to the root filesystem of the exopc machine.

Remember that exopc mounts a root filesystem via NFS when it starts up. ``install'' copies files into this root filesystem on the server. In order to tell the makefiles where to copy files you have to set the EXODEST environment variable. This points to the top of a directory-tree that will later be your exopc root directory. For example, you may have /home/pinckney/exopc as the top of you exopc source directory and point EXODEST to /home/pinckney/exopc-root. Then, when you run ``gmake install'' from /home/pinckney/exopc, /home/pinckney/exopc-root will be populated with subdirectories bin/, etc/, usr/ etc and binaries will be copied into the correct places.

The following lists some caveats of the current build process:

• Technically ``gmake install'' should build any out of date programs and then install them, but this doesn't always seem to work. To be on the safe-side, do a ``gmake; gmake install''.
• Until you understand all the cross dependencies between different parts of the system, do full builds of the entire source tree.
• Most binaries are linked against the shared library libexeos.so. Thus, if you change any of the libraries, rebuild the shared library in bin/shlib and then rebuild all of the binaries.
• The first program is special cased and resides in ebin/. The section on booting contains more information about selecting which of these programs to use as the first process. In any advent, the environment variable INITPROG can be set to choose among rconsoled, kbdinit, and bootp. If this program changes you need to rebuild the kernel in sys/ to relink the first program into the kernel.