Build Procedure

Once you have edited the graph.comp file to include all protocols and device drivers to be configured into the x-kernel , an instance of the x-kernel can be built. Execute the following steps. (The protocol table and ROM files can be specified and even changed at a later time because they are read at runtime.)

1. Put /usr/xkernel/bin/BINTYPE and /usr/xkernel/bin in your search path, where BINTYPE is one of sunos-sparc, solaris-sparc, osf1-alpha, linux-alpha, linux-x86 or irix-mips.

   These must occur before /bin and /usr/bin. This allows use of the version of make distributed with the x-kernel (GNU make v. 3.66), which is included in the BINTYPE directory, rather than the standard Unix make.

2. Modify the Makefile in the build directory. The variable XRT in this Makefile must be a path to the root of the x-kernel source tree; e.g., /usr/xkernel. The x-kernel uses a trace package to generate debugging information; to enable the tracing facility, set the Makefile variable HOWTOCOMPILE to DEBUG. To obtain accurate performance timings, variable HOWTOCOMPILE should be assigned OPTIMIZE. This causes all trace of tracing code to be eliminated from the kernel.

3. Type: make compose

   If this is the first time make compose has been run, you may see what appear to be error messages about missing files, such as Makefile.local and DEPS/Makedep.*. These warnings can be ignored, since these files will be created by the running of make compose.

4. Type: make depend

5. Type: make

Object files will be placed in a subdirectory of the OBJS directory, whose name reflects the chosen configuration and platform (e.g., UL-DEBUG-sunos-sparc). Object files are stored similarly throughout the x-kernel hierarchy. The final x-kernel executable (xkernel) will be placed in your build directory.

Steps 3 through 5 must be repeated whenever you change the graph.comp file. If the Makefile is changed, only step 5 must be repeated. Changes to the protocol tables and ROM files do not require rebuilding tke x-kernel .