1999-09-27 16:37:33 +00:00
|
|
|
Each SAPI backend has to contain:
|
|
|
|
|
|
|
|
config.m4: just like for extensions, this file contains
|
2000-11-02 16:15:03 +00:00
|
|
|
autoconf directives that end up in the configure script. The
|
1999-09-27 16:37:33 +00:00
|
|
|
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
|
1999-10-04 15:18:26 +00:00
|
|
|
two variables: PHP_SAPI (which sapi backend to choose) and INSTALL_IT
|
|
|
|
(the actions performed when "make install" is executed). If they are
|
|
|
|
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":
|
1999-09-27 16:37:33 +00:00
|
|
|
|
2000-11-02 16:15:03 +00:00
|
|
|
PHP_BUILD_SHARED -- build shared target $SAPI_SHARED
|
|
|
|
PHP_BUILD_STATIC -- build static target $SAPI_STATIC
|
|
|
|
PHP_BUILD_PROGRAM -- build executable $SAPI_PROGRAM
|
1999-10-04 15:18:26 +00:00
|
|
|
|
|
|
|
(paths relative to top build dir)
|