You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by Stephen Clouse <st...@theiqgroup.com> on 2002/06/07 21:32:07 UTC
modperl2 Header Files?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have noticed that modperl2 at the moment does not install any header files as
did its predecessor. Is this a permanent change? Because it seems rather
unworkable for any type of XS function that wants to access the API.
For example, I'm attempting to port Apache::Request (bored of waiting on an
official release, plus I have nothing better to do today since the file server
containing our company's CVS tree crashed last night :) It wants to typemap the
Apache::RequestRec and APR::Table objects. It seems odd that modperl would
provide the typemap (in PERL_LIB/Apache2/typemap) but then offer no way of
linking against the functions necessary for it to be of any use.
Some advice on the modperl2 equivalents of the above would be most helpful.
- --
Stephen Clouse <st...@theiqgroup.com>
Senior Programmer, IQ Coordinator Project Lead
The IQ Group, Inc. <http://www.theiqgroup.com/>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAj0BCjYACgkQA4aoazQ9p2dTbQCgnhtnNNrUvtqNZqZtWW57Uen4
b2kAnRQgfhmsgkoOlalNXfS5HHp8Edbu
=zURr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [OT] Re: modperl2 Header Files?
Posted by Stas Bekman <st...@stason.org>.
Issac Goldstand wrote:
>>
>>> For example, I'm attempting to port Apache::Request (bored of waiting
>>> on an official release, plus I have nothing better to do today since
>>> the file server containing our company's CVS tree crashed last night
>>> :) It wants to typemap the Apache::RequestRec and APR::Table
>>> objects. It seems odd that modperl would provide the typemap (in
>>> PERL_LIB/Apache2/typemap) but then offer no way of linking against
>>> the functions necessary for it to be of any use.
>>
>>
>>
>> I've ported the c apreq to 2.0 already (posted to the apreq list), but
>> you don't need to port the perl part. It'll be automagically created
>> by WrapXS (most of it) once it's a part of httpd.
>>
>
> OK - This is seriously bugging me because I keep hearing about WrapXS
> and it sounds really neat - but I'm missing some basics - how does it
> differ from the existing XS code, what exactly will it do, etc? Can
> someone get me started off here?
Gerald has posted his essay here very timely, read his docs and I wrote
some docs here, though they aren't complete of course:
http://perl.apache.org/release/docs/2.0/devel/core_explained/core_explained.html
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
[OT] Re: modperl2 Header Files?
Posted by Issac Goldstand <ma...@beamartyr.net>.
>
>> For example, I'm attempting to port Apache::Request (bored of waiting
>> on an official release, plus I have nothing better to do today since
>> the file server containing our company's CVS tree crashed last night
>> :) It wants to typemap the Apache::RequestRec and APR::Table
>> objects. It seems odd that modperl would provide the typemap (in
>> PERL_LIB/Apache2/typemap) but then offer no way of linking against
>> the functions necessary for it to be of any use.
>
>
> I've ported the c apreq to 2.0 already (posted to the apreq list), but
> you don't need to port the perl part. It'll be automagically created
> by WrapXS (most of it) once it's a part of httpd.
>
OK - This is seriously bugging me because I keep hearing about WrapXS
and it sounds really neat - but I'm missing some basics - how does it
differ from the existing XS code, what exactly will it do, etc? Can
someone get me started off here?
Thanks,
Issac
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: modperl2 Header Files?
Posted by Stephen Clouse <st...@theiqgroup.com>.
On Sat, Jun 08, 2002 at 04:17:20AM +0800, Stas Bekman wrote:
> If you say you are bored why don't you port Apache::src :)
I already did :) At least the inc method (which you need to build just
about anything). If you can think of more to add on to this, be my guest.
Also, if you can forward me that Apache::Request stuff, I would be most
appreciative. I believe that's the only major thing keeping my apps from
running under modperl-2.0.
--
Stephen Clouse <st...@theiqgroup.com>
Senior Programmer, IQ Coordinator Project Lead
The IQ Group, Inc. <http://www.theiqgroup.com/>
Re: modperl2 Header Files?
Posted by Stas Bekman <st...@stason.org>.
Stephen Clouse wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have noticed that modperl2 at the moment does not install any header files as
> did its predecessor. Is this a permanent change? Because it seems rather
> unworkable for any type of XS function that wants to access the API.
The Apache::src equivalent is not implemented yet. That's probably the
next thing I'll do after I'll finish up with a few urgent matters.
> For example, I'm attempting to port Apache::Request (bored of waiting on an
> official release, plus I have nothing better to do today since the file server
> containing our company's CVS tree crashed last night :) It wants to typemap the
> Apache::RequestRec and APR::Table objects. It seems odd that modperl would
> provide the typemap (in PERL_LIB/Apache2/typemap) but then offer no way of
> linking against the functions necessary for it to be of any use.
I've ported the c apreq to 2.0 already (posted to the apreq list), but
you don't need to port the perl part. It'll be automagically created by
WrapXS (most of it) once it's a part of httpd.
> Some advice on the modperl2 equivalents of the above would be most helpful.
If you say you are bored why don't you port Apache::src :)
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org