Building dynamic modules on Windows operating systems
This section provides information on building dynamic modules on Windows operating systems. This information includes identifying source files, building a module and identifying restrictions. Links to related topics appear at the end of this section.
To write a module that works with the server for Windows operating systems, use the header files included when you install the IBM HTTP Server. See Building dynamic shared object modules or dynamic link libraries with the IBM HTTP Server for more detailed information.
Identifying source files included in the installation
Installing the source code also creates an src directory in the server root directory. This directory contains the following directories:
- include: Contains the majority of header files used to create the IBM binary distribution of the Web server.
- os\win32: Contains platform-specific includes for the Windows platform distribution of the Web server.
- CoreR: Contains the library, ApacheCore.lib. Linking to this library enables your module to run with the binary distribution of the IBM HTTP Server.
- modules\example: Contains an example module and project file that demonstrate how to build a module. The project file, .dsp, was created with Microsoft Visual C++ V6.0.
Building a module
To build a module:
- Add the src\include directory to your list of include paths.
- Link with the ApacheCore.lib file, found in the Release directory.
Identifying restrictions
The following restrictions apply, when building a module to run with the IBM HTTP Server:
- You must link against the ApacheCore.lib binary installed by the server installation program in the Release directory.
- You must use the header files supplied by the server installation program in the src\include and Os\win32 directories.
- You cannot modify or add fields to the header files in the src\include or Os\win32 directories.
(Back to the top)