The attached patch (because it has \t embedded) enables the installation of src/modules/perl/*.h and xs/*.h files, because we need them to be installed for XS extensions to be built.

First of all I'm not sure if that's the right way to install these, but it works for me.

Second, I've chosen to install them to $APACHE_INSTALL_DIR/include in parallel with $APACHE_INSTALL_DIR/modules where we install mod_perl.so to. Is this a good choice, or do we want to install it under the perl lib tree as in mod_perl 1.0? Me thinking that it's nice to have all the headers in the same location (we have the ap_ and apr_ headers there already) and we don't need to mess with Apache2 prefixes here. The potential drawback that I could see is the various packaging approaches which will have to know where apache is installed.

__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

Attachment: diff
Description: application/java-vm

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to