Appendix C: Creating C Components

Procedure for generating C component files

To generate C component files from a package or component, start EAServer Manager and complete these tasks:

Select the component or, if you want to generate files for all components in a package, select the package.
Select File | Generate Stub/Skeleton. The Generate Stubs and Skeletons wizard is displayed.
Select the Generate Skeletons check box. Unless you wish to generate stubs at the same time, deselect Generate Stubs. Enter values in the Skeletons Generation Options area as follows:
- C/C++ Code Base
  
  Enter the top-level directory path for the stub files. The path must be a valid UNIX or Windows path. It can include a drive and as many directories as you want.
  
  If you clear the field, the default is the directory specified by $HOME on UNIX and %HOMEPATH% for Windows.
  
  Sybase recommends that you specify the full path to the C code base directory. If you specify a relative path, it is created under the EAServer installation directory, relative to the html/classes subdirectory.
- Java Code Base
  
  If you are generating skeletons for a package that contains both Java and C components, specify the location where generated Java skeletons are to be created. Otherwise, you can leave this field alone.
  
  WARNING! Do not use the component name as the method file name. The component name is already used for the method skeletons file.
Click Generate. EAServer Manager generates a method implementation file name, and create and destroy routine templates appended with .new.
Rename the generated method implementation template files, deleting .new.