----- Original Message -----
From: Gerald Richter <[EMAIL PROTECTED]>
To: Matt Sergeant <[EMAIL PROTECTED]>; Randy Kobes
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, September 02, 2000 3:46 AM
Subject: Re: AxKit working on ActivePerl
> > Gerald
> > - do you just write .def files by hand?
> >
>
> Yes, it is very simple. Here is an example from a project I have made some
> time ago. It exports one symbol:
Here is a possible .def file that seems to work for
both AxKit and libapreq:
#########################################
LIBRARY
EXPORTS
sv2request_rec
perl_request_rec
mod_perl_tie_table
perl_cmd_perl_FLAG
perl_cmd_perl_TAKE2
perl_cmd_perl_TAKE1
perl_cmd_perl_TAKE123
perl_perl_cmd_cleanup
#######################################
The first 3 are for libapreq, and the remaining are
for AxKit. This file should be saved in the mod_perl
source as ApacheModulePerl.def, in the directory
src\modules\ApacheModulePerl. As well, in
ApacheModulePerl.dsp, the line
SOURCE=.\ApacheModulePerl.def
should be added, in the section where the other
source files are specified. Using the APM.lib generated
in this way (after reinstalling APM.dll) results in
both libapreq and AxKit building OK and working,
at least with some simple tests.
I'm using VC++ 6 - perhaps that's why no leading
underscore was needed in the def file, as Gerald
had. Also, I didn't have the library name explicit in
this def file, as it was picked up later, and with the
name in the def file a warning about a duplicate
name resulted.
best regards,
randy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
