php-src/build/config-stubs

#!/bin/sh

dir=$1; shift
for stubfile in $dir/*/config0.m4 $dir/*/config.m4 $dir/*/config9.m4; do
    echo "dnl Define where extension directories are located in the configure context
AC_DEFUN([PHP_EXT_BUILDDIR], [`dirname $stubfile`])
AC_DEFUN([PHP_EXT_DIR], [`dirname $stubfile`])
AC_DEFUN([PHP_EXT_SRCDIR], [\$abs_srcdir/`dirname $stubfile`])
sinclude($stubfile)"
done
First commit of re-structuring phase one. We have started using automake in sub-directories and started to move extension code into ext/<name>. For now, I have moved the "standard" extension (which is quite a mix of everything right now) and the GD extension into their own subdirs in ext/. The configure script now also runs configure in the libzend directory automatically and makes sure php4 and libzend use the same config.cache file. To avoid running configure in libzend, use the --no-recursion option. "make" in php4 also builds libzend now. The Apache module doesn't compile right now, but a fix for that is coming up. 1999-04-17 08:37:12 +08:00			`#!/bin/sh`

Generalized server-API build process on UNIX. Each SAPI implementation now has its own directory under sapi/, just like extensions have theirs under ext/. To make the final targets appear in the main dir, the top-level Makefile includes sapi/NN/Makefile.inc from the selected sapi backend. This is a plan Makefile stub without any autoconf substitutions. Each SAPI backend also has its own config.m4 like extensions (read at the end of diversion 2) and config.h.stub files. 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 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 SAPI_TARGET (the name of the resulting library or program, previously BINNAME). If they are not specified, they will default to "cgi" and "php", respectively. Makefile.inc: has to exist, has to define "INSTALL_IT" to the command used to install the final target (or ":" for no operation). It also has to define a plain Makefile rule (without autoconf substitutions) to build $(SAPI_TARGET) Makefile.am: just what you think. Make sure your target is called "libphpsapi_NNN.a", where NNN is the value of PHP_SAPI. Some testing and fixing probably remains. To make everything hang together, I've done some ugly tricks that I can imagine causing some problems. I've built and run the CGI version and built the Apache DSO. 1999-09-28 00:34:28 +08:00			`dir=$1; shift`
- Add one 'level' more (0 first, 9 last) # Sascha, maybe we should use that apache2 config-stubs instead? 2002-10-21 11:07:23 +08:00			`for stubfile in $dir//config0.m4 $dir//config.m4 $dir/*/config9.m4; do`
Fixed bug #70899 (buildconf failure in extensions) 2015-11-18 04:06:39 +08:00			`echo "dnl Define where extension directories are located in the configure context`
			AC_DEFUN([PHP_EXT_BUILDDIR], [`dirname $stubfile`])
			AC_DEFUN([PHP_EXT_DIR], [`dirname $stubfile`])
			AC_DEFUN([PHP_EXT_SRCDIR], [\$abs_srcdir/`dirname $stubfile`])
Remove assumption that extensions are in ext/ext-name Fixes also a weird ln (symlink) hack for phpdbg 2014-11-03 06:25:49 +08:00			`sinclude($stubfile)"`
First commit of re-structuring phase one. We have started using automake in sub-directories and started to move extension code into ext/<name>. For now, I have moved the "standard" extension (which is quite a mix of everything right now) and the GD extension into their own subdirs in ext/. The configure script now also runs configure in the libzend directory automatically and makes sure php4 and libzend use the same config.cache file. To avoid running configure in libzend, use the --no-recursion option. "make" in php4 also builds libzend now. The Apache module doesn't compile right now, but a fix for that is coming up. 1999-04-17 08:37:12 +08:00			`done`