Doug,
I communicated with Randy yesterday regarding this issue, and I told him the wrong
answer. Now, after removing all the EXPORT
macros from the code and adding a sample .def file, both mod_perl and libapreq build
okay. After some perusing in MSDN, I found this
paragraph:
Using __
dougm 00/09/29 09:33:41
Modified:.Changes
src/modules/perl mod_perl.c perl_util.c
Log:
fix Apache::exit() so it does it does not trigger a warning
Revision ChangesPath
1.540 +1 -1 modperl/Changes
Index: Changes
===
On Thu, 28 Sep 2000, Jiho Hahm wrote:
> [omitted previous messages]
>
> Yep, by defining MODPERL_EXPORTS in every .c file that gets compiled into mod_perl,
> those .c files will see the MODPERL_API_EXPORT functions as exports (being exported
> from the binary that the source file will end up in)
