Re: [PHP4BETA] Getting UNIX uptodate

From: Date: Mon, 26 Apr 1999 21:30:59 +0000
Subject: Re: [PHP4BETA] Getting UNIX uptodate
References: 1  Groups: php.version4 
Request: Send a blank email to php-version4+get-567@lists.php.net to get a copy of this message
On wednesday I'm up to it. Right now I have a very hot fire under my feet. We're launching something big in a few days. - Stig Zeev Suraski wrote: > > The UNIX build is almost up to date, basically, the only thing that's > missing for the CGI version is compilation and linkage of cgi_main.c. I > could easily get around this by always compiling and linking it, and > selectively #ifdef'ing the code away if we're not compiling a CGI, but I > don't think that's the right way. > > With a small one last push, Stig, I think we can get it 100% modular which > would end up being the best for everybody. I guess it involves some > automake hacking though :) > > I think that both the CGI build and the Apache build, or for that matter, > any build, should generate just libphp4.a. Then, we could simply have > cgi_main.c sitting in php4_cgi, with a different Makefile, that compiles > and links a CGI binary, much like Apache compiles and links a PHP module. > > The Makefile for the CGI can probably be generated always, regardless of > whether or not we're building an Apache module or an NSAPI module or > whatever. I guess the best approach would be to simply allow any number of > modules to be built (i.e., CGI, Apache, fhttpd, NSAPI, whatever we end up > having), when the CGI Makefile is always generated, and the rest gets > generated only if you turn on an option (because not everybody would have > every server available). > > Are you up to it, Stig? > > One other thing that I think we should do is separate SAPI to a different > library, at least that was the original intent. I didn't do it just now > since I didn't want to add in unnecessary complexity, but if there's a > concensus about it, SAPI.[ch] should break up to have their own directory > with configure.in and configure.in.in whatnot :) > > And one last thing, really, is the thread safety mode. Is it difficult to > have --enable-thread-safety add -DZTS (that's obvious, even I know how to > do that), but more importantly, use the .cpp rule for generating the scanner? > > Zeev > -- > Zeev Suraski <zeev@zend.com> http://www.zend.com/ > For a PGP public key, finger bourbon@netvision.net.il > > -- > PHP 4 Beta -- PHP 4 Beta

« previous php.version4 (#567) next »