For Windows, you must build a DLL so that C functions use the standard C calling function.
EAServer Manager generates a make.nt file when you generate the component skeleton. (See “Generate C component files” for instructions on generating code with EAServer Manager.)
The generated makefile assumes that the ODBC header files and libraries can be found in one of the following locations:
The directory specified by the ODBCHOME environment variable, or
If ODBCHOME is not set, C:\msdev, which is the default installation directory for Microsoft Visual C++.
The makefile links the following import libraries:
libjaguar.lib – Contains import definitions for routines called by generated skeleton routines.
libjcm.lib – Contains import definitions for Connection Manager routines.
libjdispatch.lib – Contains import definitions for EAServer C routines.
If your code calls routines defined in other import libraries, you will need to rename and edit the generated makefile to use the additional import libraries. If you edit the generated make.nt file, rename the edited version so that it is not overwritten if you regenerate the skeleton files.To use the generated makefile, run this command from a command window while in your component’s source directory:
nmake -f make.nt
After building the DLL, copy it to the cpplib directory of your EAServer installation.
