version 1.2, 2010/07/02 00:53:06
|
version 1.3, 2010/07/02 20:36:51
|
|
|
This directory contains C-module code. There is one .c file per module. |
This directory contains C-module code. There is one .c file per module. The Rules.mk |
The Rules.mk file tells 'make' how to build modules from these .c files. |
file tells 'make' how to build modules from these .c files. There is only one .c file |
There is only one .c file checked into CVS: mymod.c. It is to serve as |
checked into CVS: mymod.c. It is to serve as a template for development. Please feel |
a template for development. Please feel free to edit mymod.c directly, |
free to edit mymod.c directly, but do not check-in changes to mymod.c to CVS. |
but do not check-in changes to mymod.c to CVS. |
|
| |
By default, the Rules.mk file defines two template modules: a |
By default, the Rules.mk file defines two template modules: a direct-connect module |
direct-connect module (mymod) and a socket-connect module (mymod_sock). |
(mymod) and a socket-connect module (mymod_sock). You can edit the file mymod.c to |
You can edit the file mymod.c to alter the behavior of this template |
alter the behavior of this template and to test out new code. |
and to test out new code. |
|
| |
To build both modules: | To build both modules: |
| |
|
|
make mymod | make mymod |
make mymod_sock | make mymod_sock |
| |
To add a new module, edit Rules.mk in this directory, following the |
To add a new module, edit Rules.mk in this directory, following the directions |
directions in that file. Please notice the comments that start with |
in that file. Please notice the comments that start with NOTE. They describe |
NOTE. They describe how to define a new module, and how to add library |
how to define a new module, and how to add library dependencies. 'Making' a newly |
dependencies. 'Making' a newly defined module is completely analogous |
defined module is completely analogous to the 'making' the template module mymod. |
to the 'making' the template module mymod. |
|