Re: [PHP4BETA] cvs: /php4 configure.in /php4/ext/java Makefile.in config.m4 /php4/sapi/servlet Makefile.in
| From: | Sascha Schumann | Date: | Wed, 26 Jan 2000 19:09:04 +0000 |
| Subject: | Re: [PHP4BETA] cvs: /php4 configure.in /php4/ext/java Makefile.in config.m4 /php4/sapi/servlet Makefile.in | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-9432@lists.php.net to get a copy of this message | ||
On Wed, Jan 26, 2000 at 01:47:58PM -0500, rubys@us.ibm.com wrote:
>
> It was my experience that unless enable_shared was set to yes in
> configure.in, libtool would refuse to build my code as a shared library.
> In order to get this to be set, I needed php_build_target to be set to
> shared, and the right way to do that appeared to be using the macro.
This limit was removed some weeks (months?) ago.
> > Why does not it allow Java to be a built-in module?
>
> In order to get the function to work, there are times where PHP calls into
> Java which, in turn, will call back into PHP code. There really is no way
> to call into the right entry point in a built-in module in a standalone
> executable, so I need the Java support to be a shared library.
That's questionable. There are a few platforms which do not
support exporting symbols from an executable (thus dlsym
fails), but passing pointers works anywhere.
--
Regards,
Sascha Schumann
Consultant
Attachment: [application/pgp-signature]
Attachment: [application/pgp-signature]