Re: [PHP4BETA] cvs: /php4 configure.in /php4/ext/java Makefile.in config.m4 /php4/sapi/servlet Makefile.in
| From: | rubys at us dot ibm dot com | Date: | Wed, 26 Jan 2000 16:39:50 +0000 |
| Subject: | Re: [PHP4BETA] cvs: /php4 configure.in /php4/ext/java Makefile.in config.m4 /php4/sapi/servlet Makefile.in | ||
| Groups: | php.version4 | ||
| Request: | Send a blank email to php-version4+get-9423@lists.php.net to get a copy of this message | ||
Sascha Schumann wrote:
> That's not the Right Way(TM) to do it. The m4 macros
> PHP_BUILD_XXX are reserved for SAPI modules and must not be
> used by extensions. If you want to allow shared CGI builds,
> make it optional in sapi/cgi/config.m4 (defaulting to
> static).
Just curious, on which stone tablets are these rules etched on? I can't
seem to find them anywhere... <grin>
All kidding aside, please feel free to educate me on what the Right Way(TM)
is - I'll gratefully accept anything from gentle suggestions to whacks
upside the head will do. I do believe that I made shared CGI builds are
optional, and default to static. I would like to have this triggered by
the specification of the --with-java argument as java support can only work
if built as shared libraries. It made sense to me to have the processing
of the --with-java argument done in ext/java, but I can move it to sapi/cgi
if it makes more sense to you.
By the way, I had ext/java and sapi/servlet working back in December on
both Windows and Unix platforms, and then there seemed to be wave after
wave of build process changes on Unix. At first I tried to keep up, but I
found that sometime problems would go away by themselves, and the fixes
that made sense one day did not make sense the next. Sensing a lull in the
activity, and in response to a number of requests, I made substantial
progress towards getting this working again and that's what I checked in a
week ago.
Even so, it still has a way to go. One thing I would find immensely
helpful is if someone who is involved in the Unix build process changes
could try building sapi/servlet (everything you need is freely downloadable
off of the web) at least once, and preferably periodically during or
shortly after periods of rapid change. No Java knowledge is required to
run the demo. I'll be glad to answer any questions that might arise, and
would use the information to improve the readme.
- Sam Ruby
P.S. Got your book. Thanks for the mention on the bottom left corner of
page 780!