> One advantage of having the two is that the ApacheModulePerl.lib
> in the usual mod_perl build is about 3 kB (and this is all that's
> needed for mod_perl itself), while the static mod_perl lib is
> about 960 kB.
>
When you build a DLL, like it is done now, ApacheModulePerl.lib is only used
in the linking stage for resolving symbols. It is not link into your
excuable library, so it doesn't matter if it grows.
>From my point of view it doesn't make any sense to have two versions of the
library, actualy I guess it will not work correctly, because Apache always
needs the DLL version and the DLL version and the static lib version will
_not_ share globales, which is neccessary to make mod_perl work.
What I suggest is just to add some more entries to the symbol table of the
DLL, makeing this symbols public viewable and thereby, makeing it possible
that other modules can use them. For the first step it would be the esaiest
to just creating a DEF file, so you don't have to modifiy any sources, but
can make the linker happy. In the second step it has to be decided, which
symbol belongs to the mod_perl API and should be exported by the DLL ( I
think Doug should take a look at this list), then using the API macros from
Apache would make it more portable to other platforms.
Gerald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
