From a44361a7695cc02aca01275bacca628c5d3c9dae Mon Sep 17 00:00:00 2001 From: Sascha Schumann Date: Thu, 2 Nov 2000 16:15:03 +0000 Subject: [PATCH] Update. Someone should really write better docs. =) --- sapi/README | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/sapi/README b/sapi/README index ffe79cf2f8..d9a759dd93 100644 --- a/sapi/README +++ b/sapi/README @@ -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 @@ not specified, they will default to "cgi" and "do nothing," 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) -- 2.50.1