Rough consensus and running code is the main idea behind libwww. As for all W3C OpenSource code, the purpose of libwww is to provide an environment for experimenting with extensions and new features. The focus of libwww is performance, modularity, and extensi3>
In addition to platform independent modules, there is a small Windows specific
DLL which implements the trace message generation. The DLL is called
windll.dll and contains also the definition of the global trace
flag definition.
windll.c - DLLMain to all DLLs.
wwwdll.c - instances WWW_TraceFlag. This is included
in wwwdll so that it can export the variables to the rest of the DLLs.
wwwdll.def, wwwutils.def, wwwcore.def -
def (exports) files for the DLLs of the same names.
What to do: Include
the windll.dll as a part of your project and make sure that it is built as the
first DLL.
The functions exported from a DLL are listed in the EXPORTS
section of a .def file. These can be found in the windows directory. These may also be build by the
makeDefs.pl perl script, see the
description below. You can use the def files as a basis for generating the DLL
projects for your compiler.
What to do: Generate
the DLLs according to the def files so the exported interface is identical to
the set of functions defined in the actual c files included in the DLL.
Unfortunately, make files are not easily shared among different C compilers on Windows which complicates the distribution. See the installation instructions for details on possible ways of building libwww on windows.