cvs: phpdoc-he /chapters install.windows.xml
[email protected] ("Hadar Porat")
| Newsgroups | php.doc.he |
|---|---|
| Message-ID | <cvshadar_p1033843650@cvsserver> |
hadar_p Sat Oct 5 14:47:30 2002 EDT
Added files:
/phpdoc-he/chapters install.windows.xml
Log:
First version - for testing cvs only
hadar_p-20021005144730.txt
(text/plain, 32.4 KB)
Index: phpdoc-he/chapters/install.windows.xml
+++ phpdoc-he/chapters/install.windows.xml
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.1 $ -->
<sect1 id="install.windows">
<title>äú÷ðä òì îòøëåú Windows</title>
<para>
çì÷ æä éùéí ì- Windows 95/98/Me å- Windows NT/2000/XP.
àì úöôä î- PHP ìòáåã òì ôìèôåøîåú ùì
16 áéè ëîå Windows 3.1. ìôòîéí
àðçðå îúééçñéí ìîòøëåú ä- Windows äðúîëåú ë- Win32
</para>
<para>
There are two main ways to install PHP for Windows: either
<link linkend="install.windows.manual">manually</link>
or by using the <link linkend="install.windows.installer">InstallShield</link>
installer.
</para>
<para>
If you have Microsoft Visual Studio, you can also
<link linkend="install.windows.build">build</link>
PHP from the original source code.
</para>
<para>
Once you have PHP installed on your Windows system, you may also
want to <link linkend="install.windows.extensions">load various extensions</link>
for added functionality.
</para>
<sect2 id="install.windows.installer">
<title>Windows InstallShield</title>
<para>
The Windows PHP installer available from the downloads page at
<ulink url="&url.php;">&url.php;</ulink>, this installs the CGI version
of PHP and, for IIS, PWS, and Xitami, configures the web server as
well. Also note, that while the InstallShield installer is an
easy way to make PHP work, it is restricted in many aspects, as
automatic setup of extensions for example is not supported.
</para>
<simpara>
Install your selected <acronym>HTTP</acronym> server on your system
and make sure that it works.
</simpara>
<simpara>
Run the executable installer and follow the instructions provided by
the installation wizard. Two types of installation are supported -
standard, which provides sensible defaults for all the settings it
can, and advanced, which asks questions as it goes along.
</simpara>
<simpara>
The installation wizard gathers enough information to set up the
&php.ini; file and configure the web server to
use PHP. For IIS and also PWS on NT Workstation, a list of all the
nodes on the server with script map settings is displayed, and you
can choose those nodes to which you wish to add the PHP script
mappings.
</simpara>
<simpara>
Once the installation has completed the installer will inform you
if you need to restart your system, restart the server, or just
start using PHP.
</simpara>
<warning>
<para>
Be aware, that this setup of PHP is not secure. If you would
like to have a secure PHP setup, you'd better go on the manual
way, and set every option carefully. This automatically working
setup gives you an instantly working PHP installation, but it is
not meant to be used on online servers.
</para>
</warning>
</sect2>
<sect2 id="install.windows.manual">
<title>Manual Installation Steps</title>
<simpara>
This install guide will help you manually install and configure
PHP on your Windows webserver. You need to download the
zip binary distribution from the downloads page at
<ulink url="&url.php;">&url.php;</ulink>. The original version
of this guide was compiled by &link.bob;, and can be found at <ulink
url="&url.win32install;">&url.win32install;</ulink>.
</simpara>
<para>
This guide provides manual installation support for:
<itemizedlist>
<listitem>
<para>
Personal Web Server 3 and 4 or newer
</para>
</listitem>
<listitem>
<para>
Internet Information Server 3 and 4 or newer
</para>
</listitem>
<listitem>
<para>
Apache 1.3.x
</para>
</listitem>
<listitem>
<para>
OmniHTTPd 2.0b1 and up
</para>
</listitem>
<listitem>
<para>
Oreilly Website Pro
</para>
</listitem>
<listitem>
<para>
Xitami
</para>
</listitem>
<listitem>
<para>
Netscape Enterprise Server, iPlanet
</para>
</listitem>
</itemizedlist>
</para>
<para>
PHP 4 for Windows comes in two flavours - a CGI executable (php.exe),
and several SAPI modules (for example: php4isapi.dll). The latter form
is new to PHP 4, and provides significantly improved performance and
some new functionality.
</para>
<warning>
<simpara>
The SAPI modules have been significantly improved in the 4.1 release,
however, you may find that you encounter possible server errors or
other server modules such as ASP failing, in older systems.
</simpara>
</warning>
<simpara>
If you choose one of the SAPI modules and use Windows 95, be sure
to download the DCOM update from the <ulink
url="&url.dcom.update;">Microsoft DCOM pages</ulink>. For the
ISAPI module, an ISAPI 4.0 compliant Web server is required
(tested on IIS 4.0, PWS 4.0 and IIS 5.0). IIS 3.0 is
<emphasis>NOT</emphasis> supported. You should download and
install the Windows NT 4.0 Option Pack with IIS 4.0 if you
want native PHP support.
</simpara>
<para>
The following steps should be performed on all installations
before the server specific instructions.
<itemizedlist>
<listitem>
<simpara>
Extract the distribution file to a directory of your choice.
<filename>c:\php\</filename> is a good start. You probably
do not want to use a path in which spaces are included (for
example: c:\program files\php is not a good idea). Some
web servers will crash if you do.
</simpara>
</listitem>
<listitem>
<simpara>
You need to ensure that the DLLs which PHP uses can be found.
The precise DLLs involved depend on which web server you use
and whether you want to run PHP as a CGI or as a server module.
<filename>php4ts.dll</filename> is always used. If you are
using a server module (e.g. ISAPI or Apache) then you will
need the relevant DLL from the <filename>sapi</filename>
folder. If you are using any PHP extension DLLs then you
will need those as well. To make sure that the DLLs can be
found, you can either copy them to the system directory
(e.g. <filename>winnt/system32</filename> or
<filename>windows/system</filename>) or you can make sure
that they live in the same directory as the main PHP
executable or DLL your web server will use (e.g.
<filename>php.exe</filename>, <filename>php4apache.dll</filename>).
</simpara>
<para>
The PHP binary, the SAPI modules, and some extensions rely on
external DLLs for execution. Make sure that these DLLs in the
distribution exist in a directory that is in the Windows PATH.
The best bet to do it is to copy the files below into your
system directory, which is typically:
<simplelist>
<member>
<filename>c:\windows\system</filename> for Windows 9x/ME
</member>
<member>
<filename>c:\winnt\system32</filename> for Windows NT/2000
</member>
<member>
<filename>c:\windows\system32</filename> for Windows XP
</member>
</simplelist>
The files to copy are:
<simplelist>
<member>
<filename>php4ts.dll</filename>, if it already exists there,
overwrite it
</member>
<member>
The files in your distribution's 'dlls' directory.
If you have them already installed on your system, overwrite them
only if something doesn't work correctly (Before overwriting them,
it is a good idea to make a backup of them, or move them to
another folder - just in case something goes wrong).
</member>
</simplelist>
</para>
<para>
Download the latest version of the Microsoft Data Access Components
(MDAC) for your platform, especially if you use Microsoft Windows
9x/NT4. MDAC is available at <ulink url="&url.mdac;">&url.mdac;</ulink>.
</para>
</listitem>
<listitem>
<para>
Copy your chosen ini file (see below) to your
'%WINDOWS%' directory on Windows 9x/Me or to your
'%SYSTEMROOT%' directory under Windows NT/2000/XP
and rename it to &php.ini;. Your
'%WINDOWS%' or '%SYSTEMROOT%' directory is
typically:
<simplelist>
<member><filename>c:\windows</filename> for Windows 9x/ME/XP</member>
<member><filename>c:\winnt</filename> or <filename>c:\winnt40</filename> for NT/2000 servers</member>
</simplelist>
</para>
<para>
There are two ini files distributed in the zip file,
<filename>php.ini-dist</filename> and
<filename>php.ini-optimized</filename>. We advise
you to use <filename>php.ini-optimized</filename>,
because we optimized the default settings in this
file for performance, and security. The best is to
study all the <link linkend="configuration.file">ini
settings</link> and set every element manually yourself.
If you would like to achieve the best security, then this
is the way for you, although PHP works fine with these
default ini files.
</para>
</listitem>
<listitem>
<para>
Edit your new &php.ini; file:
<itemizedlist>
<listitem>
<simpara>
You will need to change the 'extension_dir' setting to
point to your php-install-dir, or where you have placed
your <filename>php_*.dll</filename> files. Please do not
forget the last backslash. ex:
<filename>c:\php\extensions\</filename>
</simpara>
</listitem>
<listitem>
<simpara>
If you are using OmniHTTPd, do not follow the next step.
Set the 'doc_root' to point to your webservers
document_root. For example: <filename>c:\apache\htdocs</filename>
or <filename>c:\webroot</filename>
</simpara>
</listitem>
<listitem>
<simpara>
Choose which extensions you would like to load when PHP
starts. See the section about
<link linkend="install.windows.extensions">Windows
extensions</link>, about how to set up one, and what
is already built in. Note that on a new installation
it is advisable to first get PHP working and tested
without any extensions before enabling them in
&php.ini;.
</simpara>
</listitem>
<listitem>
<simpara>
On PWS and IIS, you can set the <filename>browscap.ini</filename>
to point to:
<filename>c:\windows\system\inetsrv\browscap.ini</filename> on
Windows 9x/Me,
<filename>c:\winnt\system32\inetsrv\browscap.ini</filename> on
NT/2000, and
<filename>c:\windows\system32\inetsrv\browscap.ini</filename>
on XP.
</simpara>
</listitem>
<listitem>
<simpara>
Note that the <filename>mibs</filename> directory supplied
with the Windows distribution contains support files for
SNMP. This directory should be moved to
<filename>DRIVE:\usr\mibs</filename> (<filename>DRIVE</filename>
being the drive where PHP is installed.)
</simpara>
</listitem>
<listitem>
<simpara>
If you're using NTFS on Windows NT, 2000 or XP, make sure that
the user running the webserver has read permissions to your
&php.ini; (e.g. make it readable by Everyone).
</simpara>
</listitem>
</itemizedlist>
</para>
</listitem>
<listitem>
<para>
For PWS give execution permission to the webroot:
<itemizedlist>
<listitem>
<simpara>
Start PWS Web Manager
</simpara>
</listitem>
<listitem>
<simpara>
Edit Properties of the "Home"-Directory
</simpara>
</listitem>
<listitem>
<simpara>
Select the "execute"-Checkbox
</simpara>
</listitem>
</itemizedlist>
</para>
</listitem>
</itemizedlist>
</para>
</sect2>
<sect2 id="install.windows.build">
<title>Building from source</title>
<para>
Before getting started, it is worthwhile answering the question:
"Why is building on Windows so hard?" Two reasons come to mind:
</para>
<orderedlist>
<listitem><simpara>
Windows does not (yet) enjoy a large community of developers
who are willing to freely share their source. As a direct
result, the necessary investment in infrastructure required
to support such development hasn't been made. By and large,
what is available has been made possible by the porting of
necessary utilities from Unix. Don't be surprised if some of
this heritage shows through from time to time.
</simpara></listitem>
<listitem><simpara>
Pretty much all of the instructions that follow are of the
"set and forget" variety. So sit back and try follow the
instructions below as faithfully as you can.
</simpara></listitem>
</orderedlist>
<sect3 id="install.windows.build.prepare">
<title>Preparations</title>
<para>
Before you get started, you have a lot to download...
</para>
<itemizedlist>
<listitem><simpara>
For starters, get the Cygwin toolkit from the closest <ulink
url="http://sources.redhat.com/cygwin/download.html">cygwin</ulink>
mirror site. This will provide you most of the popular GNU
utilities used by the build process.
</simpara></listitem>
<listitem><simpara>
Download the rest of the build tools you will need from the PHP
site at <ulink url="http://www.php.net/extra/win32build.zip"
>http://www.php.net/extra/win32build.zip</ulink>.
</simpara></listitem>
<listitem><simpara>
Get the source code for the DNS name resolver used by PHP
at <ulink url="http://www.php.net/extra/bindlib_w32.zip"
>http://www.php.net/extra/bindlib_w32.zip</ulink>. This
is a replacement for the <filename>resolv.lib</filename>
library included in <filename>win32build.zip</filename>.
</simpara></listitem>
<listitem><simpara>
If you don't already have an unzip utility, you will
need one. A free version is available from <ulink
url="http://www.cdrom.com/pub/infozip/UnZip.html">InfoZip</ulink>.
</simpara></listitem>
<listitem><simpara>If you plan to compile PHP as a static Apache
module you will also need the
<ulink url="http://httpd.apache.org/dist/httpd/">Apache sources</ulink>
of your version of Apache.
</simpara></listitem>
</itemizedlist>
<simpara>
Finally, you are going to need the source to PHP 4 itself.
You can get the latest development version using <ulink
url="http://www.php.net/anoncvs.php">anonymous CVS</ulink>. If you get
a <ulink url="http://snaps.php.net/">snapshot</ulink> or a <ulink
url="http://www.php.net/downloads.php">source</ulink> tarball, you
not only will have to untar and ungzip it, but you will have to
convert the bare linefeeds to crlf's in the <filename>*.dsp</filename>
and <filename>*.dsw</filename> files before Microsoft Visual C++
will have anything to do with them.
</simpara>
<note>
<simpara>
Place the <filename>Zend</filename> and
<filename>TSRM</filename> directories inside the
<filename>php4</filename> directory in order for the projects
to be found during the build process.
</simpara>
</note>
</sect3>
<sect3 id="install.windows.build.install">
<title>Putting it all together</title>
<itemizedlist>
<listitem><simpara>
Follow the instructions for installing the unzip utility of
your choosing.
</simpara>
</listitem>
<listitem>
<simpara>
Execute <filename>setup.exe</filename> and follow the installation
instructions. If you choose to install to a path other than
<filename>c:\cygnus</filename>, let the build process know by setting
the Cygwin environment variable. On Windows 95/98 setting
an environment variable can be done by placing a line in
your <filename>autoexec.bat</filename>. On Windows NT, go to My
Computer => Control Panel => System and select the
environment tab.
</simpara>
</listitem>
</itemizedlist>
<warning>
<simpara>
Make a temporary directory for Cygwin to use, otherwise many
commands (particularly bison) will fail. On Windows 95/98,
<userinput>mkdir C:\TMP</userinput>. For Windows NT,
<userinput>mkdir %SystemDrive%\tmp</userinput>.
</simpara>
</warning>
<itemizedlist>
<listitem>
<simpara>
Make a directory and unzip <filename>win32build.zip</filename> into it.
</simpara></listitem>
<listitem>
<simpara>
Launch Microsoft Visual C++, and from the menu select
Tools => Options. In the dialog, select the
directories tab. Sequentially change the dropdown
to Executables, Includes, and Library files,
and ensure that <filename>cygwin\bin</filename>,
<filename>win32build\include</filename>, and
<filename>win32build\lib</filename> are in each list,
respectively. (To add an entry, select a blank line
at the end of the list and begin typing). Typical entries
will look like this:
</simpara>
<itemizedlist>
<listitem><simpara>
<filename>c:\cygnus\bin</filename>
</simpara></listitem>
<listitem><simpara>
<filename>c:\php-win32build\include</filename>
</simpara></listitem>
<listitem><simpara>
<filename>c:\php-win32build\lib</filename>
</simpara></listitem>
</itemizedlist>
<simpara>
Press OK, and exit out of Visual C++.
</simpara>
</listitem>
<listitem>
<simpara>
Make another directory and unzip <filename>bindlib_w32.zip</filename>
into it. Decide whether you want to have debug symbols available
(bindlib - Win32 Debug) or not (bindlib - Win32 Release).
Build the appropriate configuration:
</simpara>
<itemizedlist>
<listitem><simpara>
For GUI users, launch VC++, and then select File => Open
Workspace and select bindlib. Then select Build=>Set
Active Configuration and select the desired configuration.
Finally select Build=>Rebuild All.
</simpara></listitem>
<listitem>
<simpara>
For command line users, make sure that you either have
the C++ environment variables registered, or have run
<command>vcvars.bat</command>, and then execute one of the
following:
</simpara>
<itemizedlist>
<listitem>
<simpara>
<userinput>msdev bindlib.dsp /MAKE "bindlib - Win32 Debug"</userinput>
</simpara>
</listitem>
<listitem>
<simpara>
<userinput>msdev bindlib.dsp /MAKE "bindlib - Win32 Release"</userinput>
</simpara>
</listitem>
</itemizedlist>
</listitem>
<listitem><simpara>
At this point, you should have a usable
<filename>resolv.lib</filename> in either your
<filename>Debug</filename> or <filename>Release</filename>
subdirectories. Copy this file into your
<filename>win32build\lib</filename> directory over the
file by the same name found in there.
</simpara></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</sect3>
<sect3 id="install.windows.build.compile">
<title>Compiling</title>
<simpara>
The best way to get started is to build the standalone/CGI version.
</simpara>
<itemizedlist>
<listitem><simpara>
For GUI users, launch VC++, and then select File => Open
Workspace and select php4ts. Then select Build=>Set Active
Configuration and select the desired configuration. Finally
select Build=>Rebuild All.
</simpara></listitem>
<listitem>
<simpara>
For command line users, make sure that you either have
the C++ environment variables registered, or have run
<command>vcvars.bat</command>, and then execute one of the
following:
</simpara>
<itemizedlist>
<listitem><simpara>
<userinput>msdev php4ts.dsp /MAKE "php4ts - Win32 Debug_TS"</userinput>
</simpara></listitem>
<listitem><simpara>
<userinput>msdev php4ts.dsp /MAKE "php4ts - Win32 Release_TS"</userinput>
</simpara></listitem>
<listitem><simpara>
At this point, you should have a usable
<filename>php.exe</filename> in either
your <filename>Debug_TS</filename> or
<filename>Release_TS</filename> subdirectories.
</simpara></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<simpara>
Repeat the above steps with <filename>php4isapi.dsp</filename>
(which can be found in <filename>sapi\isapi</filename>) in
order to build the code necessary for integrating PHP with
Microsoft IIS.
</simpara>
<simpara>
It is possible to do minor customization to the build process by editing
the main/config.win32.h.in file.
</simpara>
</sect3>
</sect2>
<sect2 id="install.windows.extensions">
<title>Installation of Windows extensions</title>
<para>
After installing PHP and a webserver on Windows, you will
probably want to install some extensions for added functionality.
The following table describes some of the extensions available. You
can choose which extensions you would like to load when PHP starts
by uncommenting the: 'extension=php_*.dll' lines in
&php.ini;. You can also load a module dynamically
in your script using <function>dl</function>.
</para>
<para>
The DLLs for PHP extensions are prefixed with 'php_' in PHP 4 (and
'php3_' in PHP 3). This prevents confusion between PHP extensions
and their supporting libraries.
</para>
<note>
<para>
In PHP 4.0.6 BCMath, Calendar, COM, FTP, MySQL, ODBC, PCRE,
Session, WDDX and XML support is <emphasis>built in</emphasis>.
You don't need to load any additional extensions in order to
use these functions. See your distributions
<filename>README.txt</filename> or <filename>install.txt</filename>
for a list of built in modules.
</para>
</note>
<note>
<para>
Some of these extensions need extra DLLs to work. Couple of them can be
found in the distribution package, in the 'dlls' folder but
some, for example Oracle (php_oci8.dll) require DLLs which are
not bundled with the distribution package.
</para>
<para>
Copy the bundled DLLs from 'DLLs' folder to your Windows
PATH, safe places are:
<simplelist>
<member>c:\windows\system for Windows 9x/Me</member>
<member>c:\winnt\system32 for Windows NT/2000</member>
<member>c:\windows\system32 for Windows XP</member>
</simplelist>
If you have them already installed on your system, overwrite them
only if something doesn't work correctly (Before overwriting them,
it is a good idea to make a backup of them, or move them to
another folder - just in case something goes wrong).
</para>
</note>
<para>
<table>
<title>PHP Extensions</title>
<tgroup cols="3">
<thead>
<row>
<entry>Extension</entry>
<entry>Description</entry>
<entry>Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry>php_bz2.dll</entry>
<entry><link linkend="ref.bzip2">bzip2</link> compression functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_calendar.dll</entry>
<entry><link linkend="ref.calendar">Calendar</link> conversion functions</entry>
<entry>Built in since PHP 4.0.3</entry>
</row>
<row>
<entry>php_cpdf.dll</entry>
<entry><link linkend="ref.cpdf">ClibPDF</link> functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_crack.dll</entry>
<entry><link linkend="ref.crack">Crack</link> functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php3_crypt.dll</entry>
<entry>Crypt functions</entry>
<entry>unknown</entry>
</row>
<row>
<entry>php_ctype.dll</entry>
<entry><link linkend="ref.ctype">ctype</link> family functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_curl.dll</entry>
<entry><link linkend="ref.curl">CURL</link>, Client URL library functions</entry>
<entry>Requires: libeay32.dll, ssleay32.dll (bundled)</entry>
</row>
<row>
<entry>php_cybercash.dll</entry>
<entry><link linkend="ref.cybercash">Cybercash</link> payment functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_db.dll</entry>
<entry><link linkend="ref.dbm">DBM</link> functions</entry>
<entry>Deprecated. Use DBA instead (php_dba.dll)</entry>
</row>
<row>
<entry>php_dba.dll</entry>
<entry><link linkend="ref.dba">DBA</link>: DataBase (dbm-style) Abstraction layer functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_dbase.dll</entry>
<entry><link linkend="ref.dbase">dBase</link> functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php3_dbm.dll</entry>
<entry>Berkeley DB2 library</entry>
<entry>unknown</entry>
</row>
<row>
<entry>php_domxml.dll</entry>
<entry><link linkend="ref.domxml">DOM XML</link> functions</entry>
<entry>Requires: libxml2.dll (bundled)</entry>
</row>
<row>
<entry>php_dotnet.dll</entry>
<entry><link linkend="ref.dotnet">.NET</link> functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_exif.dll</entry>
<entry><link linkend="function.read-exif-data">Read EXIF</link> headers from JPEG</entry>
<entry>None</entry>
</row>
<row>
<entry>php_fbsql.dll</entry>
<entry><link linkend="ref.fbsql">FrontBase</link> functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_fdf.dll</entry>
<entry><link linkend="ref.fdf">FDF</link>: Forms Data Format functions.</entry>
<entry>Requires: fdftk.dll (bundled)</entry>
</row>
<row>
<entry>php_filepro.dll</entry>
<entry><link linkend="ref.filepro">filePro</link> functions</entry>
<entry>Read-only access</entry>
</row>
<row>
<entry>php_ftp.dll</entry>
<entry><link linkend="ref.ftp">FTP</link> functions</entry>
<entry>Built-in since PHP 4.0.3</entry>
</row>
<row>
<entry>php_gd.dll</entry>
<entry><link linkend="ref.image">GD</link> library image functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_gettext.dll</entry>
<entry><link linkend="ref.gettext">Gettext</link> functions</entry>
<entry>Requires: gnu_gettext.dll (bundled)</entry>
</row>
<row>
<entry>php_hyperwave.dll</entry>
<entry><link linkend="ref.hyperwave">HyperWave</link> functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_iconv.dll</entry>
<entry><link linkend="ref.iconv">ICONV</link> characterset conversion</entry>
<entry>Requires: iconv-1.3.dll (bundled)</entry>
</row>
<row>
<entry>php_ifx.dll</entry>
<entry><link linkend="ref.ifx">Informix</link> functions</entry>
<entry>Requires: Informix libraries</entry>
</row>
<row>
<entry>php_iisfunc.dll</entry>
<entry>IIS management functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_imap.dll</entry>
<entry><link linkend="ref.imap">IMAP</link> POP3 and NNTP functions</entry>
<entry>PHP 3: php3_imap4r1.dll</entry>
</row>
<row>
<entry>php_ingres.dll</entry>
<entry><link linkend="ref.ingres">Ingres II</link> functions</entry>
<entry>Requires: Ingres II libraries</entry>
</row>
<row>
<entry>php_interbase.dll</entry>
<entry><link linkend="ref.ibase">InterBase</link> functions</entry>
<entry>Requires: gds32.dll (bundled)</entry>
</row>
<row>
<entry>php_java.dll</entry>
<entry><link linkend="ref.java">Java</link> extension</entry>
<entry>Requires: jvm.dll (bundled)</entry>
</row>
<row>
<entry>php_ldap.dll</entry>
<entry><link linkend="ref.ldap">LDAP</link> functions</entry>
<entry>Requires: libsasl.dll (bundled)</entry>
</row>
<row>
<entry>php_mhash.dll</entry>
<entry><link linkend="ref.mhash">Mhash</link> Functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_ming.dll</entry>
<entry><link linkend="ref.ming">Ming</link> functions for Flash</entry>
<entry>None</entry>
</row>
<row>
<entry>php_msql.dll</entry>
<entry><link linkend="ref.msql">mSQL</link> functions</entry>
<entry>Requires: msql.dll (bundled)</entry>
</row>
<row>
<entry>php3_msql1.dll</entry>
<entry>mSQL 1 client</entry>
<entry>unknown</entry>
</row>
<row>
<entry>php3_msql2.dll</entry>
<entry>mSQL 2 client</entry>
<entry>unknown</entry>
</row>
<row>
<entry>php_mssql.dll</entry>
<entry><link linkend="ref.mssql">MSSQL</link> functions</entry>
<entry>Requires: ntwdblib.dll (bundled)</entry>
</row>
<row>
<entry>php3_mysql.dll</entry>
<entry><link linkend="ref.mysql">MySQL</link> functions</entry>
<entry>Built-in in PHP 4</entry>
</row>
<row>
<entry>php3_nsmail.dll</entry>
<entry>Netscape mail functions</entry>
<entry>unknown</entry>
</row>
<row>
<entry>php3_oci73.dll</entry>
<entry>Oracle functions</entry>
<entry>unknown</entry>
</row>
<row>
<entry>php_oci8.dll</entry>
<entry><link linkend="ref.oci8">Oracle 8</link> functions</entry>
<entry>Requires: Oracle 8 client libraries</entry>
</row>
<row>
<entry>php_openssl.dll</entry>
<entry><link linkend="ref.openssl">OpenSSL</link> functions</entry>
<entry>Requires: libeay32.dll (bundled)</entry>
</row>
<row>
<entry>php_oracle.dll</entry>
<entry><link linkend="ref.oracle">Oracle</link> functions</entry>
<entry>Requires: Oracle 7 client libraries</entry>
</row>
<row>
<entry>php_pdf.dll</entry>
<entry><link linkend="ref.pdf">PDF</link> functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_pgsql.dll</entry>
<entry><link linkend="ref.pgsql">PostgreSQL</link> functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_printer.dll</entry>
<entry><link linkend="ref.printer">Printer</link> functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_xslt.dll</entry>
<entry><link linkend="ref.xslt">XSLT</link> functions</entry>
<entry>Requires: sablot.dll (bundled)</entry>
</row>
<row>
<entry>php_snmp.dll</entry>
<entry><link linkend="ref.snmp">SNMP</link> get and walk functions</entry>
<entry>NT only!</entry>
</row>
<row>
<entry>php_sybase_ct.dll</entry>
<entry><link linkend="ref.sybase">Sybase</link> functions</entry>
<entry>Requires: Sybase client libraries</entry>
</row>
<row>
<entry>php_yaz.dll</entry>
<entry><link linkend="ref.yaz">YAZ</link> functions</entry>
<entry>None</entry>
</row>
<row>
<entry>php_zlib.dll</entry>
<entry><link linkend="ref.zlib">ZLib</link> compression functions</entry>
<entry>None</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</sect2>
</sect1>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:"../../manual.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
-->