cvs: php4 /sapi README
| From: | Sascha Schumann | Date: | Thu, 02 Nov 2000 16:15:04 +0000 |
| Subject: | cvs: php4 /sapi README | ||
| Groups: | php.cvs | ||
| Request: | Send a blank email to php-cvs+get-2417@lists.php.net to get a copy of this message | ||
sas Thu Nov 2 08:15:04 2000 EDT
Modified files:
/php4/sapi README
Log:
Update. Someone should really write better docs. =)
Index: php4/sapi/README
diff -u php4/sapi/README:1.4 php4/sapi/README:1.5
--- php4/sapi/README:1.4 Sun Aug 27 03:05:23 2000
+++ php4/sapi/README Thu Nov 2 08:15:03 2000
@@ -1,7 +1,7 @@
Each SAPI backend has to contain:
config.m4: just like for extensions, this file contains
-autoconf/automake directives that end up in the configure script. The
+autoconf directives that end up in the configure script. The
only difference is that the sapi config.m4 files are read in diversion
(output block) 2 instead of 3. The sapi config.m4 files should set
two variables: PHP_SAPI (which sapi backend to choose) and INSTALL_IT
@@ -10,8 +10,8 @@
respectively. Additionally, the following m4 macros can be used to
influence what is created during "make":
-PHP_BUILD_SHARED -- build shared target libs/libphp4.so
-PHP_BUILD_STATIC -- build static target libs/libphp4.a
-PHP_BUILD_PROGRAM -- build executable php
+PHP_BUILD_SHARED -- build shared target $SAPI_SHARED
+PHP_BUILD_STATIC -- build static target $SAPI_STATIC
+PHP_BUILD_PROGRAM -- build executable $SAPI_PROGRAM
(paths relative to top build dir)