.\" @(#)rpcgen.1 2.2 88/08/02 4.0 RPCSRC
.TH RPCGEN 1 "18 January 1988"
rpcgen \- an RPC protocol compiler
.BR \-c \|| \|\-h \|| \|\-l \||\fB\|\-m
.IX "compilers" rpcgen "" "\fLrpcgen\fR \(em generate RPC protocols, C header files"
.IX rpcgen "" "\fLrpcgen\fR \(em generate RPC protocol, C header files, and server skeleton"
.IX RPC "generate protocols \(em \fLrpcgen\fR"
is a tool that generates C
is a language similar to C
Language (Remote Procedure Call Language). Information
Language is available in the
.RI ` rpcgen ' " Programming Guide."
is normally used as in the first synopsis where it takes an input file
and generates four output files. If the
will generate a header file in
The other synopses shown above are used when one does not want to
generate all the output files, but only a particular one. Their
usage is described in the
is run on all input files before they are actually
directives are legal within an
input file. For each type of output file,
defined when compiling into header files
defined when compiling into
defined when compiling into server-side stubs
defined when compiling into client-side stubs
does a little preprocessing of its own.
is passed directly into the output file, uninterpreted by
You can customize some of your
routines by leaving those data
types undefined. For every data type that is undefined,
will assume that there exists a routine with the name
prepended to the name of the undefined type.
data-definitions (a header file)
Compile into client-side stubs.
Compile into server-side stubs, but do not generate a \(lqmain\(rq routine.
This option is useful for doing callback-routines and for people who
need to write their own \(lqmain\(rq routine to do initialization.
Specify the name of the output file.
If none is specified, standard output is used
Compile into server-side stubs, using the the given transport. The
This option may be invoked more than once
so as to compile a server that serves multiple transports.
.RI ` rpcgen ' " Programming Guide."
Nesting is not supported.
As a work-around, structures can be declared at
top-level, and their name used inside other structures in order to achieve
Name clashes can occur when using program definitions, since the apparent
scoping does not really apply. Most of these can be avoided by giving
unique names for programs, versions, procedures and types.