Filter
Top Products
Section 5 Specifications of a Config File
Rev. 1.01 Mar. 17, 2008 Page 23 of 128
REJ10J1822-0101
Section 5 Specifications of a Config File
A config file contains definitions used for creation of the client and server stubs. Specifically, such
definitions are made by appending keywords for passing to RPCGEN to the API of the server
functions (as described in section 6, Definitions of Server Functions). Read this section carefully
before creating your own config file. The extension for config files is “.x.”
One config file corresponds to the definition of one server. Do not attempt to define multiple
servers within a single config file.
5.1 Definition
Definitions must be written in either of the following formats.
<keyword>{...};
<keyword>;
For certain definitions, two or more items can be entered between the braces {...}.
Example:
GLOBAL_INCFILE { “types.h” “rpc_public.h” };
A config file can include the following definitions.
(1) Locations where the files created by RPCGEN will be stored
• PUB_INCPATH{…}; Path to <config file>_public.h
• CLNT_SOURCEPATH{…}; Path to <config file>_clnt.c
• CLNT_INCPATH{…}; Path to <config file>_clnt.h and <config file>_private.h
• SVR_SOURCEPATH{…}; Path to <config file>_svr.c
• SVR_INCPATH{…}; Path to <config file>_svr.h
(2) Controlling output of the #include directive to the files created by RPCGEN
• GLOBAL_INCFILE{…}; Include file common to the client and server stubs
• CLNT_INCFILE{…}; Include file for the client stub
• SVR_INCFILE{…}; Include file for the server stub