cvs: phpdoc /ja/chapters install.xml
| From: | Rui Hirokawa | Date: | Sun, 04 Feb 2001 01:47:53 +0000 |
| Subject: | cvs: phpdoc /ja/chapters install.xml | ||
| Groups: | php.doc | ||
| Request: | Send a blank email to phpdoc+get-969334142@lists.php.net to get a copy of this message | ||
hirokawa Sat Feb 3 17:47:53 2001 EDT
Modified files:
/phpdoc/ja/chapters install.xml
Log:
update translation.
Index: phpdoc/ja/chapters/install.xml diff -u phpdoc/ja/chapters/install.xml:1.22 phpdoc/ja/chapters/install.xml:1.23 --- phpdoc/ja/chapters/install.xml:1.22 Tue Jan 16 06:46:06 2001 +++ phpdoc/ja/chapters/install.xml Sat Feb 3 17:47:53 2001 @@ -358,14 +358,14 @@ </simpara> </sect2> <sect2 id="install.macosx.compile"> - <title>Compiling for OS X server</title> + <title>OS X ãµã¼ãã§ã®ã³ã³ãã¤ã«</title> <simpara> There are two slightly different versions of Mac OS X, client and server. The following is for OS X server. </simpara> <example id="install.macosx.compile.example"> <title> - Mac OS X server install + Mac OS X ãµã¼ãã§ã®ã¤ã³ã¹ãã¼ã« </title> <programlisting> 1. Get the latest distributions of Apache and PHP @@ -447,7 +447,6 @@ <sect1 id="install.configure"> <title>è¨å®ãªãã·ã§ã³ã®å®å ¨ãªãªã¹ã</title> - <note> <para> ãããã®ãªãã·ã§ã³ã¯ãã³ã³ãã¤ã«æã«ã®ã¿ä½¿ç¨å¯è½ã§ããPHPã®å®è¡è¨ @@ -1244,7 +1243,6 @@ </listitem> </varlistentry> </variablelist> - </sect2> <sect2 id="install.configure.graphics"> @@ -1727,8 +1725,8 @@ </term> <listitem> <para> - PHP 3, PHP 4: make rules ãæå¹ã«ããä¾åæ§ã¯ã«ã¸ã¥ã¢ã«ã¤ã³ã¹ - ãã¼ã«ã«æç¨ã§ã¯ããã¾ãã (ããããæ··ä¹±ãã¾ã)ã + PHP 3, PHP 4: make rules ããã³ dependencies ãæå¹ã«ãã¾ãã + ä¸è¬çãªã¤ã³ã¹ãã¼ã«ã§ã¯å¿ è¦ããã¾ãã(æ··ä¹±ãããã¨ãããã¾ã)ã </para> </listitem> </varlistentry> @@ -2848,29 +2846,28 @@ </sect1> - <sect1 id="install-windows95-nt"> - <title>Windows 95/98/NT ã·ã¹ãã ã¸ã®ã¤ã³ã¹ãã¼ã«</title> + <sect1 id="install-windows"> + <title>Windows 9x/Me/NT/2000ã·ã¹ãã ã¸ã®ã¤ã³ã¹ãã¼ã«</title> <para> - PHPãWindowsã«ã¤ã³ã¹ãã¼ã«ããã«ã¯ãããã¥ã¢ã«ã¤ã³ã¹ãã¼ã«ã¨ - installshieldã¤ã³ã¹ãã¼ã«ã«ããæ¹æ³ã®2種é¡ãããã¾ãã - <itemizedlist> - <listitem> - <simpara> - <link linkend="install.windows.installer">Installshield</link> - ã«é¢ããæé ã¯ãã¡ããåç §ä¸ããã - </simpara> - </listitem> - <listitem> - <simpara> - <link linkend="install.windows.manual">ããã¥ã¢ã«è¨å®</link> - ã«é¢ããæé ã¯ãã¡ããåç §ä¸ããã - </simpara> - </listitem> - </itemizedlist> + PHPãWindowsã«ã¤ã³ã¹ãã¼ã«ããã«ã¯ã<link + linkend="install.windows.manual">ããã¥ã¢ã«ã¤ã³ã¹ãã¼ã«</link>ã¨ã¤ + ã³ã¹ãã¼ã©<link + linkend="install.windows.installer">InstallShield</link>ã«ããæ¹æ³ + ã®2種é¡ãããã¾ãã </para> + <para> + Microsoft Visual Studioãæã£ã¦ããå ´åããªãªã¸ãã«ã®ã½ã¼ã¹ã³ã¼ã + ããPHPã <link linkend="install.windows.build">æ§ç¯</link>ããã + ã¨ãå¯è½ã§ãã + </para> + <para> + Windowsã·ã¹ãã ã«PHPãã¤ã³ã¹ãã¼ã«ããå¾ãæ©è½ã追å ããããã« + <link linkend="install.windows.extensions">æ§ã ãªæ¡å¼µã¢ã¸ã¥ã¼ã«ã® + ãã¼ã</link>ãè¡ãå¯è½æ§ãããã¾ãã + </para> <sect2 id="install.windows.installer"> - <title>Windows Installshield</title> + <title>Windows InstallShield</title> <para> CGIãã¼ã¸ã§ã³ã®PHPãã¤ã³ã¹ãã¼ã«ãã Windows ç¨ PHPã¤ã³ã¹ãã¼ã©ãã @@ -2879,8 +2876,8 @@ </para> <simpara> - 使ç¨ããHTTPãµã¼ãã¼ãã·ã¹ãã ã«ã¤ã³ã¹ãã¼ã«ããå®å ¨ã«åä½ããã - ãã«ãã¦ä¸ããã + 使ç¨ãã<acronym>HTTP</acronym>ãµã¼ãã¼ãã·ã¹ãã ã«ã¤ã³ã¹ãã¼ã«ãã + å®å ¨ã«åä½ããããã«ãã¦ä¸ããã </simpara> <simpara> @@ -2909,8 +2906,8 @@ <sect2 id="install.windows.manual"> <title>ä¸è¬çãªã¤ã³ã¹ãã¼ã«æé </title> <simpara> - ãã®ã¤ã³ã¹ãã¼ã«æé ã¯ãWindows 9x/NT Webãµã¼ãã«ã¤ãã¦PHPãæå - ã§ã¤ã³ã¹ãã¼ã«ããè¨å®ãéã®æå©ãã¨ãªããã®ã§ãããã®æå¼ã¯ã + ãã®ã¤ã³ã¹ãã¼ã«æé ã¯ãWindows 9x/Me/NT/2000ä¸ã®Webãµã¼ãã«PHPã + æåã§ã¤ã³ã¹ãã¼ã«ããè¨å®ãéã®æå©ãã¨ãªããã®ã§ãããã®æå¼ã¯ã &link.bob;ã«ããæ¸ããããã®ã§ãããªãªã¸ãã«çã¯ã<ulink url="&url.win32install;">&url.win32install;</ulink>ã«ããã¾ãã </simpara> @@ -2919,26 +2916,62 @@ <itemizedlist> <listitem> <para> - Personal Web Server (ææ°çãæ¨å¥¨) + Personal Web Server 3ã¾ãã¯4以é </para> </listitem> <listitem> - <para> - Internet Information Server 3 ã¾ã㯠4 - </para> - </listitem> - <listitem> - <para> - Apache 1.3.x - </para> - </listitem> - <listitem> - <para> - Omni HTTPd 2.0b1 - </para> - </listitem> - </itemizedlist> - </para> + <para> + Internet Information Server 3 ã¾ã㯠4以é + </para> + </listitem> + <listitem> + <para> + Apache 1.3.x + </para> + </listitem> + <listitem> + <para> + Omni HTTPd 2.0b1 以é + </para> + </listitem> + <listitem> + <para> + Oreilly Website Pro + </para> + </listitem> + <listitem> + <para> + Xitami + </para> + </listitem> + </itemizedlist> + </para> + <para> + PHP 4 for Windows comes in two flavours - a CGI executable (php.exe), + and several SAPI modules (for exapmle php4isapi.dll). The latter form + is new to PHP 4, and provides significantly improved performance and + some new functionality. However, please note that the SAPI modules + are <emphasis>NOT</emphasis> yet considered to be production quality. + The reason for this is that the PHP SAPI modules are using the + thread-safe version of the PHP code, which is new to PHP 4, and has + not yet been tested and pounded enough to be considered completely + stable, and there are actually a few known bugs. On the other hand, + some people have reported very good results with the SAPI modules, + even though we're not aware of anyone actually running it on a + production site. In short - your mileage may vary; If you need + absolute stability, trade the performance of the SAPI modules + with the stability of the CGI executable. + </para> + <para> + If you choose one of the SAPI modules and use Windows 95, be sure + to download the DCOM update from the <ulink + url="http://download.microsoft.com/msdownload/dcom/95/x86/en/dcom95.exe">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. + </para> <para> 以ä¸ã®æé ã¯ãåã ã®ãµã¼ãã¼ã«é¢ããæé ã®åã«è¡ãå ¨ã¦ã®ã¤ã³ã¹ãã¼ ã«ã«å ±éããå¿ é ã®ãã®ã§ãã @@ -2984,25 +3017,25 @@ </listitem> <listitem> <simpara> - PHP å®è¡éå§æã«ãã¼ããããã¢ã¸ã¥ã¼ã«ã鏿ãã¦ä¸ããã - ãããã®ã¢ã¸ã¥ã¼ã«ããã¼ãããããã«ã¯ã'extension=php_*.dll' ã® - è¡ããã³ã¡ã³ããå¤ãã¾ãã - ããã¤ãã®ã¢ã¸ã¥ã¼ã«ã¯ãæ£å¸¸ã«åä½ããããã«è¿½å ã®ã©ã¤ãã©ãªã® - ã¤ã³ã¹ãã¼ã«ãå¿ è¦ã¨ãã¾ãã - PHP <ulink url="&url.php.faq;">FAQ</ulink>ã«ã¯ã - ãµãã¼ãç¨ã©ã¤ãã©ãªã®å¨ãå¦ã«é¢ããæ´ã«è©³ç´°ãªæ å ±ã - è¨è¼ããã¦ãã¾ãã - ã¹ã¯ãªããã®ä¸ã§ä»¥ä¸ã®ã³ãã³ãã«ããåçã«ã¢ã¸ã¥ã¼ã«ã - ãã¼ããããã¨ãã§ãã¾ãã - <command>dl("php_*.dll");</command> + PHP å®è¡éå§æã«ãã¼ããããã¢ã¸ã¥ã¼ã«ã鏿ãã¦ä¸ãããã + ããã®ã¢ã¸ã¥ã¼ã«ããã¼ãããããã«ã¯ã'extension=php_*.dll' + ã®è¡ããã³ã¡ã³ããå¤ãã¾ããããã¤ãã®ã¢ã¸ã¥ã¼ã«ã¯ãæ£å¸¸ã« + åä½ããããã«è¿½å ã®ã©ã¤ãã©ãªã®ã¤ã³ã¹ãã¼ã«ãå¿ è¦ã¨ãã¾ãã + PHP <ulink url="&url.php.faq;">FAQ</ulink>ã«ã¯ããµãã¼ãç¨ + ã©ã¤ãã©ãªã®å¨ãå¦ã«é¢ããæ´ã«è©³ç´°ãªæ å ±ãè¨è¼ããã¦ãã¾ãã + ã¹ã¯ãªããã®ä¸ã§<function>dl</function>ã使ç¨ãããã¨ã«ãã + åçã«ã¢ã¸ã¥ã¼ã«ããã¼ããããã¨ãã§ãã¾ãã + <link linkend="install.windows.extensions">Windows + æ¡å¼µã¢ã¸ã¥ã¼ã«</link>ã«é¢ããç¯ãåç §ä¸ããã </simpara> </listitem> <listitem> <simpara> - PWS 㨠IIS ã«ããã¦ã¯ãbrowscap.ini ãæ¬¡ã®ããã«æå®ãããã¨ã - ã§ãã¾ãã - Windows 95/98 ã§ã¯ 'c:\windows\system\inetsrv\browscap.ini' ã - ãã㦠NT ãµã¼ãã¼ã§ã¯ 'c:\winnt\system32\inetsrv\browscap.ini' + PWS 㨠IIS ã«ããã¦ã¯ã<filename>browscap.ini</filename>ã + 次ã®ããã«æå®ãããã¨ãã§ãã¾ãã: + Windows 9x/Me ã§ã¯ 'c:\windows\system\inetsrv\browscap.ini' ã + NT/2000 ãµã¼ãã¼ã§ã¯ + 'c:\winnt\system32\inetsrv\browscap.ini' PHP ã«ããã browscap æ©è½ã«é¢ããè©³ç´°ãªæ å ±ã«ã¤ãã¦ã¯ã ãã® <ulink url="&url.browscap;">ãã©ã¼ãµã¼ãã¼</ulink> ãè¦ã¦ã "source" ãã¿ã³ãæ¼ãã¦åä½ã確èªä¸ããã @@ -3011,34 +3044,261 @@ </itemizedlist> </para> </listitem> - </itemizedlist></para> - <simpara> - PHPæ¡å¼µæ©è½ç¨ã®DLLã«ã¯ã'php_'ãå é ã«ã¤ãã¦ãã¾ããããã«ããã - PHPæ¡å¼µæ©è½ç¨ãã¡ã¤ã«ã¨ãµãã¼ãç¨ã©ã¤ãã©ãªã¨ãééãããã¨ã鲿¢ - ãã¾ãã - </simpara> + </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> + </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 autoexec.bat. On Windows NT, go to My Computer => + Control Panel => System and select the environment tab. + </simpara> + <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> + </listitem> + <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> + </sect3> </sect2> - </sect1> + <sect2 id="install.windows.extensions"> + <title>Windows ç¨æ¡å¼µã¢ã¸ã¥ã¼ã«ã®ã¤ã³ã¹ãã¼ã«</title> + <para> + PHPããã³Webãµã¼ããWindowsã«ã¤ã³ã¹ãã¼ã«ããå¾ãç¹å®ã®ã¢ã¸ã¥ã¼ã« + ã使ç¨ããããªãå ´åãããã§ãããã以ä¸ã®è¡¨ã«ç¾å¨ã®Windowã¢ã¸ã¥ã¼ + ã«ã示ãã¾ããããã¥ã¢ã«ã¤ã³ã¹ãã¼ã«æé ã§èª¬æããããã«ãPHPãèµ· + åããéã« 'extension=php_*.dll' ã®è¡ã®ã³ã¡ã³ããå¤ããã¨ã«ããã + ãã¼ãããã¢ã¸ã¥ã¼ã«ã鏿ãããã¨ãå¯è½ã§ããããã¤ãã®ã¢ã¸ã¥ã¼ã« + ã¯ãæ£ããåä½ãããããã«ã·ã¹ãã ã«å¥ã®ã©ã¤ãã©ãªãã¤ã³ã¹ãã¼ã«ã + ã¦ããå¿ è¦ãããã¾ããPHP <ulink url="&url.php.faq;">FAQ</ulink> + ã«ã¯ããµãã¼ãããã©ã¤ãã©ãªã®åå¾å ´æã«é¢ãã詳ããæ å ±ãããã¾ãã + ã¹ã¯ãªããã®ä¸ã§<function>dl</function>ã使ç¨ãããã¨ã«ããã㢠+ ã¸ã¥ã¼ã«ãåçã«ãã¼ããããã¨ãå¯è½ã§ãã + </para> + <para> + The DLLs for PHP extensions are prefixed with 'php_'. This + prevents confusion between PHP extensions and their supporting + libraries. + </para> + <note> + <para> + In PHP 4.0.4pl1 MySQL, ODBC, FTP, Calendar, BCMath, COM, 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> - <sect1 id="install-windows-modules"> - <title>Windows ã¢ã¸ã¥ã¼ã«ã®ã¤ã³ã¹ãã¼ã«</title> - <para> - PHPããã³Webãµã¼ããWindowsã«ã¤ã³ã¹ãã¼ã«ããå¾ãç¹å®ã®ã¢ã¸ã¥ã¼ã« - ã使ç¨ããããªãå ´åãããã§ãããã以ä¸ã®è¡¨ã«ç¾å¨ã®Windowã¢ã¸ã¥ã¼ - ã«ã示ãã¾ããããã¥ã¢ã«ã¤ã³ã¹ãã¼ã«æé ã§èª¬æããããã«ãPHPãèµ· - åããéã« 'extension=php_*.dll' ã®è¡ã®ã³ã¡ã³ããå¤ããã¨ã«ããã - ãã¼ãããã¢ã¸ã¥ã¼ã«ã鏿ãããã¨ãå¯è½ã§ããããã¤ãã®ã¢ã¸ã¥ã¼ã« - ã¯ãæ£ããåä½ãããããã«ã·ã¹ãã ã«å¥ã®ã©ã¤ãã©ãªãã¤ã³ã¹ãã¼ã«ã - ã¦ããå¿ è¦ãããã¾ããPHP <ulink url="&url.php.faq;">FAQ</ulink> - ã«ã¯ããµãã¼ãããã©ã¤ãã©ãªã®åå¾å ´æã«é¢ãã詳ããæ å ±ãããã¾ãã - ã¹ã¯ãªããã«æ¬¡ã®ããã«æ¸ããã¨ã«ãããã¢ã¸ã¥ã¼ã«ãåçã«ãã¼ããã - ãã¨ãå¯è½ã§ãã - <command>dl("php_*.dll");</command> - </para> - <sect2 id="install.windows.modules"> - <title>PHP ã¢ã¸ã¥ã¼ã«</title> <para> <table> <title>PHP ã¢ã¸ã¥ã¼ã«</title> @@ -3116,12 +3376,10 @@ </tgroup> </table> </para> - </sect2> - </sect1> - <sect1 id="install.apache"> + <sect1 id="install.apache"> <title>Apache ãµã¼ãã¸ã®ã¤ã³ã¹ãã¼ã«</title> <para> æ¬ç¯ã§ã¯ãPHPãApacheã«ã¤ã³ã¹ãã¼ã«ããéã®æ³¨æäºé ã¨ã³ãã«ã¤ã㦠@@ -3383,15 +3641,18 @@ </sect1> <sect1 id="install.iis"> - <title>IIS/PWS ãµã¼ãã¤ã³ã¹ãã¼ã«</title> + <title>IIS/PWS ãµã¼ãã¸ã®ã¤ã³ã¹ãã¼ã«</title> <para> - æ¬ç¯ã§ã¯ãPHPãIISã«ã¤ã³ã¹ãã¼ã«ããéã®æ³¨æããã³ã³ãã«ã¤ãã¦èª¬æ - ãã¾ãã<link linkend="install.iis.iis3">IIS3</link> ããã³ - <link linkend="install.iis.iis4">IIS4</link> ã®ä¸¡æ¹ã«ã¤ãã¦èª¬æã - ã¾ãã + æ¬ç¯ã§ã¯ãPHPãIIS(Microsoft Internet Information Server) ã«ã¤ã³ã¹ + ãã¼ã«ããéã®æ³¨æããã³ãã³ãã«ã¤ãã¦èª¬æãã¾ãã + <link linkend="install.iis.iis3">PWS/IIS 3</link>ã + <link linkend="install.iis.pws4">PWS 4 以é</link>ã + <link linkend="install.iis.iis4">IIS 4 以é</link> ã®ãã¼ã¸ã§ã³ã« + ã¤ãã¦èª¬æãã¾ãã </para> + <sect2 id="install.iis.iis3"> - <title>Windows 95/98/NT 㨠PWS/IIS 3</title> + <title>Windows 㨠PWS/IIS 3</title> <simpara> ãããã®ãµã¼ãã¼ãè¨å®ããããã«æ¨å¥¨ãããæ¹æ³ã¯ãé å¸ãã¡ã¤ã«ã« @@ -3543,67 +3804,151 @@ </sect2> + <sect2 id="install.iis.pws4"> + <title>Windowsã¨PWS 4以é</title> + + <simpara> + PWS 4以éãå®è¡ããWindowsä¸ã«PHPãã¤ã³ã¹ãã¼ã«ããéã«ã¯ãäºã¤ã® + æ¹æ³ãããã¾ããä¸ã¤ã¯ãPHP CGIãã¤ããªãè¨å®ããæ¹æ³ã§ãããä¸ã¤ + ã¯ãISAPIã¢ã¸ã¥ã¼ã« dllã使ç¨ããæ¹æ³ã§ãã + </simpara> + + <para> + If you choose the CGI binary, do the following: + <itemizedlist> + <listitem> + <simpara> + Edit the enclosed <filename>pws-php4cgi.reg</filename> + file (look into the sapi dir) to reflect the location of + your php.exe. Forward slashes should be escaped, for example: + <literal>[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w3svc\parameters\Script Map] ".php"="C:\\PHP\\php.exe"</literal> + </simpara> + </listitem> + <listitem> + <simpara> + In the PWS Manager, right click on a given directory you want + to add PHP support to, and select Properties. Check the 'Execute' + checkbox, and confirm. + </simpara> + </listitem> + </itemizedlist> + </para> + + <para> + If you choose the ISAPI module, do the following: + <itemizedlist> + <listitem> + <simpara> + Edit the enclosed <filename>pws-php4isapi.reg</filename> + file (look into the sapi dir) to reflect the location of + your php4isapi.dll. Forward slashes should be escaped, for example: + <literal>[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w3svc\parameters\Script Map] ".php"="C:\\PHP\\sapi\\php4isapi.dll"</literal> + </simpara> + </listitem> + <listitem> + <simpara> + In the PWS Manager, right click on a given directory you want to + add PHP support to, and select Properties. Check the 'Execute' + checkbox, and confirm. + </simpara> + </listitem> + </itemizedlist> + </para> + + </sect2> + <sect2 id="install.iis.iis4"> - <title>Windows NT ããã³ IIS 4</title> + <title>Windows NT/2000 and IIS 4 or newer</title> + <simpara> + To install PHP on an NT/2000 Server running IIS 4 or newer, + follow these instructions. You have two options to set up + PHP, using the CGI binary (php.exe) or with the ISAPI module. + </simpara> + <simpara> - IIS 4ãå®è¡ããNTãµã¼ãä¸ã«PHPãã¤ã³ã¹ãã¼ã«ããéã«ã¯ã以ä¸ã®æ - é ã«å¾ã£ã¦ä¸ããã + In either case, you need to start the Microsoft Management + Console (may appear as 'Internet Services Manager', either + in your Windows NT 4.0 Option Pack branch or the Control + Panel=>Administrative Tools under Windows 2000). Then + right click on your Web server node (this will most probably + appear as 'Default Web Server'), and select 'Properties'. </simpara> <para> + If you want to use the CGI binary, do the following: <itemizedlist> <listitem> <simpara> - ã¤ã³ã¿ã¼ããããµã¼ãã¹ããã¼ã¸ã£ã¼ (MMC) ã«ã¦ãWeb ãµã¤ãã¾ã - ã¯ã¢ããªã±ã¼ã·ã§ã³ã®ã¹ã¿ã¼ãä½ç½®ã¨ãªããã£ã¬ã¯ããªã鏿Wã¦ä¸ - ããã + Under 'Home Directory', 'Virtual Directory', or + 'Directory', click on the 'Configuration' button, + and then enter the App Mappings tab. </simpara> </listitem> <listitem> + <simpara> + Click Add, and in the Executable box, type: + <literal>c:\php\php.exe %s %s</literal> (assuming + that you have unziped PHP in c:\php\). You MUST + have the %s %s on the end, PHP will not function + properly if you fail to do this. + </simpara> + </listitem> + <listitem> <simpara> - ãã®ãã£ã¬ã¯ããªã®ããããã£ã·ã¼ãã(å³ã¯ãªãã¯ãã¦ããã - ããããã£ã鏿ãã¦)ãªã¼ãã³ããã¤ã¥ãã¦ããã¼ã ãã£ã¬ã¯ããªã - ä»®æ³ãã£ã¬ã¯ããªããã£ã¬ã¯ããªã¿ããã¯ãªãã¯ãã¦ä¸ããã + In the Extension box, type the file name extension you want + associated with PHP scripts. Leave 'Method exclusions' + blank, and check the Script engine checkbox. + You must repeat step 3 and 4 for each extension you + want associated with PHP scripts. + (<literal>.php</literal> and <literal>.phtml</literal> + are common.) </simpara> </listitem> <listitem> <simpara> - è¨å®ãã¿ã³ãã¯ãªãã¯ããã¤ã¥ãã¦ãã¢ããªã±ã¼ã·ã§ã³ãããã¿ãã - ã¯ãªãã¯ãã¦ä¸ããã + Set up the appropriate security. (This is done in Internet + Service Manager), and if your NT Server uses NTFS file system, + add execute rights for I_USR_ to the directory that contains + <literal>php.exe</literal>. </simpara> </listitem> + </itemizedlist> + </para> + + <para> + To use the ISAPI module, do the following: + <itemizedlist> <listitem> <simpara> - 追å (Add)ãã¯ãªãã¯ããå®è¡ãã¡ã¤ã«(Executable) ããã¯ã¹ã«ã¦ - 次ã®ããã«å ¥åãã¦ä¸ããã - <literal>c:\path-to-php-dir\php.exe %s %s</literal> - æå¾ã« %s %s ãå¿ ãä»ãã¦ãã ããã - ããããªã㨠PHP ãæ£å¸¸ã«åä½ããªãå¯è½æ§ãããã¾ãã + If you don't want to perform HTTP Authentication using PHP, + you can (and should) skip this step. Under ISAPI Filters, + add a new ISAPI filter. Use PHP as the filter name, and + supply a path to the php4isapi.dll. </simpara> </listitem> <listitem> <simpara> - æ¡å¼µåããã¯ã¹ã«ã¦ãPHP ã¹ã¯ãªããã«é¢é£ä»ããããã¡ã¤ã«æ¡å¼µå - ãå ¥åãã¦ä¸ããã - PHP ã¹ã¯ãªããã«é¢é£ä»ããã忡張å - (é常ã¯ã<literal>.php</literal> 㨠<literal>.phtml</literal> ã§ã) - ãè¨å®ããããã«ãæé 5 ããã³ 6 ãç¹°ãè¿ãã¦ãã ããã + Under 'Home Directory', click on the 'Configuration' button. + Add a new entry to the Application Mappings. Use the path + to the php4isapi.dll as the Executable, supply .php as the + extension, leave Method exclusions blank, and check the + Script engine checkbox. </simpara> </listitem> <listitem> <simpara> - ã»ãã¥ãªãã£ãé©åã«è¨å®ãã¦ä¸ããã(ãã®ä½æ¥ã¯ãã¤ã³ã¿ã¼ãã - ããµã¼ãã¹ããã¼ã¸ã£ã§è¡ãã¾ãã)NT ãµã¼ãã¼ã NTFS ãã¡ã¤ã«ã· - ã¹ãã ã使ç¨ãã¦ããå ´åãI_USR_ ã« <literal>php.exe</literal> - ããããã£ã¬ã¯ããªã®å®è¡æ¨©éãä¸ãã¦ãã ããã + Stop IIS completely </simpara> </listitem> + <listitem> + <simpara> + Start IIS again + </simpara> + </listitem> </itemizedlist> </para> - </sect2> - </sect1> <sect1 id="install.netscape-enterprise"> @@ -3628,8 +3973,8 @@ ã«æé from: bhager@invacare.com - 1. www.sunfreeware.com ã¾ãã¯ä»ã® - ãã¦ã³ãã¼ããµã¤ããã以ä¸ã®ããã±ã¼ã¸ãã¤ã³ã¹ãã¼ã«ãã¦ä¸ãã +1. www.sunfreeware.com ã¾ãã¯ä»ã®ãã¦ã³ãã¼ããµã¤ããã以ä¸ã®ããã±ã¼ + ã¸ãã¤ã³ã¹ãã¼ã«ãã¦ä¸ãã flex-2_5_4a-sol26-sparc-local gcc-2_95_2-sol26-sparc-local @@ -3643,9 +3988,9 @@ mysql-3.23.24-beta (mysql ãµãã¼ãã使ç¨ããå ´å) tar-1.13 (GNU tar) - 2. é©å½ãªãã£ã¬ã¯ããªããã¹ã«å«ã¾ãã¦ãããã©ããã確èªä¸ãã - PATH=.:/usr/local/bin:/usr/sbin:/usr/bin:/usr/ccs/bin - export PATH +2. é©å½ãªãã£ã¬ã¯ããªããã¹ã«å«ã¾ãã¦ãããã©ããã確èªä¸ãã + PATH=.:/usr/local/bin:/usr/sbin:/usr/bin:/usr/ccs/bin + export PATH 3. gunzip php-x.x.x.tar.gz (.gzé å¸ã®å ´åãããã§ãªãå ´åã¯4ã¸é²ã) 4. tar xvf php-x.x.x.tar @@ -3788,9 +4133,97 @@ <simpara> PHPã¨å ±ã«å®è¡ããã忡張æ©è½æ¯ã«æé 2ï½6 ãç¹°ãè¿ãã¾ãã </simpara> + </sect2> + </sect1> + <sect1 id="install.oreilly"> + <title>Oreilly Website Pro Server installs</title> + <para> + This section contains notes and hints specific to Oreilly + Website Pro. + </para> + <sect2 id="install.oreilly.windows"> + <title>Oreilly Website Pro 2.5 and up for Windows</title> + + <simpara> + This list describes how to set up the PHP CGI binary + or the ISAPI module to work with Oreilly Website Pro + on Windows. + </simpara> + + <para> + <itemizedlist> + <listitem> + <para> + Edit the Server Properties and select the tab "Mapping". + </para> + </listitem> + <listitem> + <para> + From the List select "Associations" and enter the desired + extension (".php") and the path to the CGI exe + (ex. c:\php\php.exe) or the ISAPI dll file + (ex. c:\php\sapi\php4isapi.dll). + </para> + </listitem> + <listitem> + <para> + Select "Content Types" add the same extension ".php" + and enter the content type. If you choose the CGI exe + file, enter 'wwwserver/shellcgi', if you chosse the + ISAPI module, enter 'wwwserver/isapi' (both without + quotes). + </para> + </listitem> + </itemizedlist> + </para> </sect2> - + </sect1> + + <sect1 id="install.xitami"> + <title>Xitami Server installs</title> + <para> + This section contains notes and hints specific to Xitami. + </para> + <sect2 id="install.xitami.windows"> + <title>Xitami for Windows</title> + + <simpara> + This list describes how to set up the PHP CGI binary + to work with Xitami on Windows. + </simpara> + + <para> + <itemizedlist> + <listitem> + <para> + Make sure the webserver is running, and point + your browser to xitamis admin console + (usually http://127.0.0.1/admin), and click on + Configuration. + </para> + </listitem> + <listitem> + <para> + Navigate to the Filters, and put the + extension which php should parse (i.e. .php) + into the field File extensions (.xxx). + </para> + </listitem> + <listitem> + <para> + In Filter command or script put the path and name + of your php executable i.e. c:\php\php.exe. + </para> + </listitem> + <listitem> + <para> + Press the 'Save' icon. + </para> + </listitem> + </itemizedlist> + </para> + </sect2> </sect1> <sect1 id="install.otherhttpd"> @@ -3800,6 +4233,8 @@ ãããµã¼ãã¼ã«é¢ä¿ããè¨å®ãªãã·ã§ã³ã®å®å ¨ãªãªã¹ãã«ã¤ãã¦ã¯ã <link linkend="install.configure.servers">ãµã¼ãã¼ã«é¢ä¿ãã ãªãã·ã§ã³</link> ãåç §ä¸ããã + The PHP CGI binaries are compatible with almost all + webservers supporting the CGI interface. </para> </sect1> @@ -3855,16 +4290,17 @@ <title>å½éå颿°ã«ã¤ãã¦</title> <simpara> - å½éå颿°ãæå¹ã«ãããã¨ã«ãããæ¥æ¬èªå¦çæã®æ¼¢åã³ã¼ãèªå夿æ©è½ã - å§ãã¨ããæç¨ãªæ©è½ãå©ç¨å¯è½ã«ãªãã¾ãã + å½éå颿°ãæå¹ã«ãããã¨ã«ãããæ¥æ¬èªå¦çæã®æ¼¢åã³ã¼ãèªåå¤ + ææ©è½ãå§ãã¨ããæç¨ãªæ©è½ãå©ç¨å¯è½ã«ãªãã¾ãã(å½éåçã®PHP + ã®ã¿å¯¾å¿) </simpara> <sect3 id="i18n-abstract"> <title>å½éå颿°ã®å ¥æ</title> <para> - PHP å½éåããã±ã¼ã¸ã¯ããPHP3å½éåãã¼ã ãã«ããç¾å¨ãã¹ãä¸ã§ã - <ulink url="http://www.happysize.co.jp/techie/php-ja-jp/"> - http://www.happysize.co.jp/techie/php-ja-jp/</ulink> + PHP å½éåããã±ã¼ã¸ã¯ããPHPå½éåããã¸ã§ã¯ããã«ããéçºããã + <ulink url="http://php.jpnnet.com/"> + http://php.jpnnet.com/</ulink> ã¾ã㯠<ulink url="ftp://ftp.happysize.co.jp/php-ja-jp/"> ftp://ftp.happysize.co.jp/php-ja-jp/</ulink>ã§æã«å ¥ãã¾ãã
Index: phpdoc/ja/chapters/install.xml diff -u phpdoc/ja/chapters/install.xml:1.22 phpdoc/ja/chapters/install.xml:1.23 --- phpdoc/ja/chapters/install.xml:1.22 Tue Jan 16 06:46:06 2001 +++ phpdoc/ja/chapters/install.xml Sat Feb 3 17:47:53 2001 @@ -358,14 +358,14 @@ </simpara> </sect2> <sect2 id="install.macosx.compile"> - <title>Compiling for OS X server</title> + <title>OS X ãµã¼ãã§ã®ã³ã³ãã¤ã«</title> <simpara> There are two slightly different versions of Mac OS X, client and server. The following is for OS X server. </simpara> <example id="install.macosx.compile.example"> <title> - Mac OS X server install + Mac OS X ãµã¼ãã§ã®ã¤ã³ã¹ãã¼ã« </title> <programlisting> 1. Get the latest distributions of Apache and PHP @@ -447,7 +447,6 @@ <sect1 id="install.configure"> <title>è¨å®ãªãã·ã§ã³ã®å®å ¨ãªãªã¹ã</title> - <note> <para> ãããã®ãªãã·ã§ã³ã¯ãã³ã³ãã¤ã«æã«ã®ã¿ä½¿ç¨å¯è½ã§ããPHPã®å®è¡è¨ @@ -1244,7 +1243,6 @@ </listitem> </varlistentry> </variablelist> - </sect2> <sect2 id="install.configure.graphics"> @@ -1727,8 +1725,8 @@ </term> <listitem> <para> - PHP 3, PHP 4: make rules ãæå¹ã«ããä¾åæ§ã¯ã«ã¸ã¥ã¢ã«ã¤ã³ã¹ - ãã¼ã«ã«æç¨ã§ã¯ããã¾ãã (ããããæ··ä¹±ãã¾ã)ã + PHP 3, PHP 4: make rules ããã³ dependencies ãæå¹ã«ãã¾ãã + ä¸è¬çãªã¤ã³ã¹ãã¼ã«ã§ã¯å¿ è¦ããã¾ãã(æ··ä¹±ãããã¨ãããã¾ã)ã </para> </listitem> </varlistentry> @@ -2848,29 +2846,28 @@ </sect1> - <sect1 id="install-windows95-nt"> - <title>Windows 95/98/NT ã·ã¹ãã ã¸ã®ã¤ã³ã¹ãã¼ã«</title> + <sect1 id="install-windows"> + <title>Windows 9x/Me/NT/2000ã·ã¹ãã ã¸ã®ã¤ã³ã¹ãã¼ã«</title> <para> - PHPãWindowsã«ã¤ã³ã¹ãã¼ã«ããã«ã¯ãããã¥ã¢ã«ã¤ã³ã¹ãã¼ã«ã¨ - installshieldã¤ã³ã¹ãã¼ã«ã«ããæ¹æ³ã®2種é¡ãããã¾ãã - <itemizedlist> - <listitem> - <simpara> - <link linkend="install.windows.installer">Installshield</link> - ã«é¢ããæé ã¯ãã¡ããåç §ä¸ããã - </simpara> - </listitem> - <listitem> - <simpara> - <link linkend="install.windows.manual">ããã¥ã¢ã«è¨å®</link> - ã«é¢ããæé ã¯ãã¡ããåç §ä¸ããã - </simpara> - </listitem> - </itemizedlist> + PHPãWindowsã«ã¤ã³ã¹ãã¼ã«ããã«ã¯ã<link + linkend="install.windows.manual">ããã¥ã¢ã«ã¤ã³ã¹ãã¼ã«</link>ã¨ã¤ + ã³ã¹ãã¼ã©<link + linkend="install.windows.installer">InstallShield</link>ã«ããæ¹æ³ + ã®2種é¡ãããã¾ãã </para> + <para> + Microsoft Visual Studioãæã£ã¦ããå ´åããªãªã¸ãã«ã®ã½ã¼ã¹ã³ã¼ã + ããPHPã <link linkend="install.windows.build">æ§ç¯</link>ããã + ã¨ãå¯è½ã§ãã + </para> + <para> + Windowsã·ã¹ãã ã«PHPãã¤ã³ã¹ãã¼ã«ããå¾ãæ©è½ã追å ããããã« + <link linkend="install.windows.extensions">æ§ã ãªæ¡å¼µã¢ã¸ã¥ã¼ã«ã® + ãã¼ã</link>ãè¡ãå¯è½æ§ãããã¾ãã + </para> <sect2 id="install.windows.installer"> - <title>Windows Installshield</title> + <title>Windows InstallShield</title> <para> CGIãã¼ã¸ã§ã³ã®PHPãã¤ã³ã¹ãã¼ã«ãã Windows ç¨ PHPã¤ã³ã¹ãã¼ã©ãã @@ -2879,8 +2876,8 @@ </para> <simpara> - 使ç¨ããHTTPãµã¼ãã¼ãã·ã¹ãã ã«ã¤ã³ã¹ãã¼ã«ããå®å ¨ã«åä½ããã - ãã«ãã¦ä¸ããã + 使ç¨ãã<acronym>HTTP</acronym>ãµã¼ãã¼ãã·ã¹ãã ã«ã¤ã³ã¹ãã¼ã«ãã + å®å ¨ã«åä½ããããã«ãã¦ä¸ããã </simpara> <simpara> @@ -2909,8 +2906,8 @@ <sect2 id="install.windows.manual"> <title>ä¸è¬çãªã¤ã³ã¹ãã¼ã«æé </title> <simpara> - ãã®ã¤ã³ã¹ãã¼ã«æé ã¯ãWindows 9x/NT Webãµã¼ãã«ã¤ãã¦PHPãæå - ã§ã¤ã³ã¹ãã¼ã«ããè¨å®ãéã®æå©ãã¨ãªããã®ã§ãããã®æå¼ã¯ã + ãã®ã¤ã³ã¹ãã¼ã«æé ã¯ãWindows 9x/Me/NT/2000ä¸ã®Webãµã¼ãã«PHPã + æåã§ã¤ã³ã¹ãã¼ã«ããè¨å®ãéã®æå©ãã¨ãªããã®ã§ãããã®æå¼ã¯ã &link.bob;ã«ããæ¸ããããã®ã§ãããªãªã¸ãã«çã¯ã<ulink url="&url.win32install;">&url.win32install;</ulink>ã«ããã¾ãã </simpara> @@ -2919,26 +2916,62 @@ <itemizedlist> <listitem> <para> - Personal Web Server (ææ°çãæ¨å¥¨) + Personal Web Server 3ã¾ãã¯4以é </para> </listitem> <listitem> - <para> - Internet Information Server 3 ã¾ã㯠4 - </para> - </listitem> - <listitem> - <para> - Apache 1.3.x - </para> - </listitem> - <listitem> - <para> - Omni HTTPd 2.0b1 - </para> - </listitem> - </itemizedlist> - </para> + <para> + Internet Information Server 3 ã¾ã㯠4以é + </para> + </listitem> + <listitem> + <para> + Apache 1.3.x + </para> + </listitem> + <listitem> + <para> + Omni HTTPd 2.0b1 以é + </para> + </listitem> + <listitem> + <para> + Oreilly Website Pro + </para> + </listitem> + <listitem> + <para> + Xitami + </para> + </listitem> + </itemizedlist> + </para> + <para> + PHP 4 for Windows comes in two flavours - a CGI executable (php.exe), + and several SAPI modules (for exapmle php4isapi.dll). The latter form + is new to PHP 4, and provides significantly improved performance and + some new functionality. However, please note that the SAPI modules + are <emphasis>NOT</emphasis> yet considered to be production quality. + The reason for this is that the PHP SAPI modules are using the + thread-safe version of the PHP code, which is new to PHP 4, and has + not yet been tested and pounded enough to be considered completely + stable, and there are actually a few known bugs. On the other hand, + some people have reported very good results with the SAPI modules, + even though we're not aware of anyone actually running it on a + production site. In short - your mileage may vary; If you need + absolute stability, trade the performance of the SAPI modules + with the stability of the CGI executable. + </para> + <para> + If you choose one of the SAPI modules and use Windows 95, be sure + to download the DCOM update from the <ulink + url="http://download.microsoft.com/msdownload/dcom/95/x86/en/dcom95.exe">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. + </para> <para> 以ä¸ã®æé ã¯ãåã ã®ãµã¼ãã¼ã«é¢ããæé ã®åã«è¡ãå ¨ã¦ã®ã¤ã³ã¹ãã¼ ã«ã«å ±éããå¿ é ã®ãã®ã§ãã @@ -2984,25 +3017,25 @@ </listitem> <listitem> <simpara> - PHP å®è¡éå§æã«ãã¼ããããã¢ã¸ã¥ã¼ã«ã鏿ãã¦ä¸ããã - ãããã®ã¢ã¸ã¥ã¼ã«ããã¼ãããããã«ã¯ã'extension=php_*.dll' ã® - è¡ããã³ã¡ã³ããå¤ãã¾ãã - ããã¤ãã®ã¢ã¸ã¥ã¼ã«ã¯ãæ£å¸¸ã«åä½ããããã«è¿½å ã®ã©ã¤ãã©ãªã® - ã¤ã³ã¹ãã¼ã«ãå¿ è¦ã¨ãã¾ãã - PHP <ulink url="&url.php.faq;">FAQ</ulink>ã«ã¯ã - ãµãã¼ãç¨ã©ã¤ãã©ãªã®å¨ãå¦ã«é¢ããæ´ã«è©³ç´°ãªæ å ±ã - è¨è¼ããã¦ãã¾ãã - ã¹ã¯ãªããã®ä¸ã§ä»¥ä¸ã®ã³ãã³ãã«ããåçã«ã¢ã¸ã¥ã¼ã«ã - ãã¼ããããã¨ãã§ãã¾ãã - <command>dl("php_*.dll");</command> + PHP å®è¡éå§æã«ãã¼ããããã¢ã¸ã¥ã¼ã«ã鏿ãã¦ä¸ãããã + ããã®ã¢ã¸ã¥ã¼ã«ããã¼ãããããã«ã¯ã'extension=php_*.dll' + ã®è¡ããã³ã¡ã³ããå¤ãã¾ããããã¤ãã®ã¢ã¸ã¥ã¼ã«ã¯ãæ£å¸¸ã« + åä½ããããã«è¿½å ã®ã©ã¤ãã©ãªã®ã¤ã³ã¹ãã¼ã«ãå¿ è¦ã¨ãã¾ãã + PHP <ulink url="&url.php.faq;">FAQ</ulink>ã«ã¯ããµãã¼ãç¨ + ã©ã¤ãã©ãªã®å¨ãå¦ã«é¢ããæ´ã«è©³ç´°ãªæ å ±ãè¨è¼ããã¦ãã¾ãã + ã¹ã¯ãªããã®ä¸ã§<function>dl</function>ã使ç¨ãããã¨ã«ãã + åçã«ã¢ã¸ã¥ã¼ã«ããã¼ããããã¨ãã§ãã¾ãã + <link linkend="install.windows.extensions">Windows + æ¡å¼µã¢ã¸ã¥ã¼ã«</link>ã«é¢ããç¯ãåç §ä¸ããã </simpara> </listitem> <listitem> <simpara> - PWS 㨠IIS ã«ããã¦ã¯ãbrowscap.ini ãæ¬¡ã®ããã«æå®ãããã¨ã - ã§ãã¾ãã - Windows 95/98 ã§ã¯ 'c:\windows\system\inetsrv\browscap.ini' ã - ãã㦠NT ãµã¼ãã¼ã§ã¯ 'c:\winnt\system32\inetsrv\browscap.ini' + PWS 㨠IIS ã«ããã¦ã¯ã<filename>browscap.ini</filename>ã + 次ã®ããã«æå®ãããã¨ãã§ãã¾ãã: + Windows 9x/Me ã§ã¯ 'c:\windows\system\inetsrv\browscap.ini' ã + NT/2000 ãµã¼ãã¼ã§ã¯ + 'c:\winnt\system32\inetsrv\browscap.ini' PHP ã«ããã browscap æ©è½ã«é¢ããè©³ç´°ãªæ å ±ã«ã¤ãã¦ã¯ã ãã® <ulink url="&url.browscap;">ãã©ã¼ãµã¼ãã¼</ulink> ãè¦ã¦ã "source" ãã¿ã³ãæ¼ãã¦åä½ã確èªä¸ããã @@ -3011,34 +3044,261 @@ </itemizedlist> </para> </listitem> - </itemizedlist></para> - <simpara> - PHPæ¡å¼µæ©è½ç¨ã®DLLã«ã¯ã'php_'ãå é ã«ã¤ãã¦ãã¾ããããã«ããã - PHPæ¡å¼µæ©è½ç¨ãã¡ã¤ã«ã¨ãµãã¼ãç¨ã©ã¤ãã©ãªã¨ãééãããã¨ã鲿¢ - ãã¾ãã - </simpara> + </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> + </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 autoexec.bat. On Windows NT, go to My Computer => + Control Panel => System and select the environment tab. + </simpara> + <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> + </listitem> + <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> + </sect3> </sect2> - </sect1> + <sect2 id="install.windows.extensions"> + <title>Windows ç¨æ¡å¼µã¢ã¸ã¥ã¼ã«ã®ã¤ã³ã¹ãã¼ã«</title> + <para> + PHPããã³Webãµã¼ããWindowsã«ã¤ã³ã¹ãã¼ã«ããå¾ãç¹å®ã®ã¢ã¸ã¥ã¼ã« + ã使ç¨ããããªãå ´åãããã§ãããã以ä¸ã®è¡¨ã«ç¾å¨ã®Windowã¢ã¸ã¥ã¼ + ã«ã示ãã¾ããããã¥ã¢ã«ã¤ã³ã¹ãã¼ã«æé ã§èª¬æããããã«ãPHPãèµ· + åããéã« 'extension=php_*.dll' ã®è¡ã®ã³ã¡ã³ããå¤ããã¨ã«ããã + ãã¼ãããã¢ã¸ã¥ã¼ã«ã鏿ãããã¨ãå¯è½ã§ããããã¤ãã®ã¢ã¸ã¥ã¼ã« + ã¯ãæ£ããåä½ãããããã«ã·ã¹ãã ã«å¥ã®ã©ã¤ãã©ãªãã¤ã³ã¹ãã¼ã«ã + ã¦ããå¿ è¦ãããã¾ããPHP <ulink url="&url.php.faq;">FAQ</ulink> + ã«ã¯ããµãã¼ãããã©ã¤ãã©ãªã®åå¾å ´æã«é¢ãã詳ããæ å ±ãããã¾ãã + ã¹ã¯ãªããã®ä¸ã§<function>dl</function>ã使ç¨ãããã¨ã«ããã㢠+ ã¸ã¥ã¼ã«ãåçã«ãã¼ããããã¨ãå¯è½ã§ãã + </para> + <para> + The DLLs for PHP extensions are prefixed with 'php_'. This + prevents confusion between PHP extensions and their supporting + libraries. + </para> + <note> + <para> + In PHP 4.0.4pl1 MySQL, ODBC, FTP, Calendar, BCMath, COM, 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> - <sect1 id="install-windows-modules"> - <title>Windows ã¢ã¸ã¥ã¼ã«ã®ã¤ã³ã¹ãã¼ã«</title> - <para> - PHPããã³Webãµã¼ããWindowsã«ã¤ã³ã¹ãã¼ã«ããå¾ãç¹å®ã®ã¢ã¸ã¥ã¼ã« - ã使ç¨ããããªãå ´åãããã§ãããã以ä¸ã®è¡¨ã«ç¾å¨ã®Windowã¢ã¸ã¥ã¼ - ã«ã示ãã¾ããããã¥ã¢ã«ã¤ã³ã¹ãã¼ã«æé ã§èª¬æããããã«ãPHPãèµ· - åããéã« 'extension=php_*.dll' ã®è¡ã®ã³ã¡ã³ããå¤ããã¨ã«ããã - ãã¼ãããã¢ã¸ã¥ã¼ã«ã鏿ãããã¨ãå¯è½ã§ããããã¤ãã®ã¢ã¸ã¥ã¼ã« - ã¯ãæ£ããåä½ãããããã«ã·ã¹ãã ã«å¥ã®ã©ã¤ãã©ãªãã¤ã³ã¹ãã¼ã«ã - ã¦ããå¿ è¦ãããã¾ããPHP <ulink url="&url.php.faq;">FAQ</ulink> - ã«ã¯ããµãã¼ãããã©ã¤ãã©ãªã®åå¾å ´æã«é¢ãã詳ããæ å ±ãããã¾ãã - ã¹ã¯ãªããã«æ¬¡ã®ããã«æ¸ããã¨ã«ãããã¢ã¸ã¥ã¼ã«ãåçã«ãã¼ããã - ãã¨ãå¯è½ã§ãã - <command>dl("php_*.dll");</command> - </para> - <sect2 id="install.windows.modules"> - <title>PHP ã¢ã¸ã¥ã¼ã«</title> <para> <table> <title>PHP ã¢ã¸ã¥ã¼ã«</title> @@ -3116,12 +3376,10 @@ </tgroup> </table> </para> - </sect2> - </sect1> - <sect1 id="install.apache"> + <sect1 id="install.apache"> <title>Apache ãµã¼ãã¸ã®ã¤ã³ã¹ãã¼ã«</title> <para> æ¬ç¯ã§ã¯ãPHPãApacheã«ã¤ã³ã¹ãã¼ã«ããéã®æ³¨æäºé ã¨ã³ãã«ã¤ã㦠@@ -3383,15 +3641,18 @@ </sect1> <sect1 id="install.iis"> - <title>IIS/PWS ãµã¼ãã¤ã³ã¹ãã¼ã«</title> + <title>IIS/PWS ãµã¼ãã¸ã®ã¤ã³ã¹ãã¼ã«</title> <para> - æ¬ç¯ã§ã¯ãPHPãIISã«ã¤ã³ã¹ãã¼ã«ããéã®æ³¨æããã³ã³ãã«ã¤ãã¦èª¬æ - ãã¾ãã<link linkend="install.iis.iis3">IIS3</link> ããã³ - <link linkend="install.iis.iis4">IIS4</link> ã®ä¸¡æ¹ã«ã¤ãã¦èª¬æã - ã¾ãã + æ¬ç¯ã§ã¯ãPHPãIIS(Microsoft Internet Information Server) ã«ã¤ã³ã¹ + ãã¼ã«ããéã®æ³¨æããã³ãã³ãã«ã¤ãã¦èª¬æãã¾ãã + <link linkend="install.iis.iis3">PWS/IIS 3</link>ã + <link linkend="install.iis.pws4">PWS 4 以é</link>ã + <link linkend="install.iis.iis4">IIS 4 以é</link> ã®ãã¼ã¸ã§ã³ã« + ã¤ãã¦èª¬æãã¾ãã </para> + <sect2 id="install.iis.iis3"> - <title>Windows 95/98/NT 㨠PWS/IIS 3</title> + <title>Windows 㨠PWS/IIS 3</title> <simpara> ãããã®ãµã¼ãã¼ãè¨å®ããããã«æ¨å¥¨ãããæ¹æ³ã¯ãé å¸ãã¡ã¤ã«ã« @@ -3543,67 +3804,151 @@ </sect2> + <sect2 id="install.iis.pws4"> + <title>Windowsã¨PWS 4以é</title> + + <simpara> + PWS 4以éãå®è¡ããWindowsä¸ã«PHPãã¤ã³ã¹ãã¼ã«ããéã«ã¯ãäºã¤ã® + æ¹æ³ãããã¾ããä¸ã¤ã¯ãPHP CGIãã¤ããªãè¨å®ããæ¹æ³ã§ãããä¸ã¤ + ã¯ãISAPIã¢ã¸ã¥ã¼ã« dllã使ç¨ããæ¹æ³ã§ãã + </simpara> + + <para> + If you choose the CGI binary, do the following: + <itemizedlist> + <listitem> + <simpara> + Edit the enclosed <filename>pws-php4cgi.reg</filename> + file (look into the sapi dir) to reflect the location of + your php.exe. Forward slashes should be escaped, for example: + <literal>[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w3svc\parameters\Script Map] ".php"="C:\\PHP\\php.exe"</literal> + </simpara> + </listitem> + <listitem> + <simpara> + In the PWS Manager, right click on a given directory you want + to add PHP support to, and select Properties. Check the 'Execute' + checkbox, and confirm. + </simpara> + </listitem> + </itemizedlist> + </para> + + <para> + If you choose the ISAPI module, do the following: + <itemizedlist> + <listitem> + <simpara> + Edit the enclosed <filename>pws-php4isapi.reg</filename> + file (look into the sapi dir) to reflect the location of + your php4isapi.dll. Forward slashes should be escaped, for example: + <literal>[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w3svc\parameters\Script Map] ".php"="C:\\PHP\\sapi\\php4isapi.dll"</literal> + </simpara> + </listitem> + <listitem> + <simpara> + In the PWS Manager, right click on a given directory you want to + add PHP support to, and select Properties. Check the 'Execute' + checkbox, and confirm. + </simpara> + </listitem> + </itemizedlist> + </para> + + </sect2> + <sect2 id="install.iis.iis4"> - <title>Windows NT ããã³ IIS 4</title> + <title>Windows NT/2000 and IIS 4 or newer</title> + <simpara> + To install PHP on an NT/2000 Server running IIS 4 or newer, + follow these instructions. You have two options to set up + PHP, using the CGI binary (php.exe) or with the ISAPI module. + </simpara> + <simpara> - IIS 4ãå®è¡ããNTãµã¼ãä¸ã«PHPãã¤ã³ã¹ãã¼ã«ããéã«ã¯ã以ä¸ã®æ - é ã«å¾ã£ã¦ä¸ããã + In either case, you need to start the Microsoft Management + Console (may appear as 'Internet Services Manager', either + in your Windows NT 4.0 Option Pack branch or the Control + Panel=>Administrative Tools under Windows 2000). Then + right click on your Web server node (this will most probably + appear as 'Default Web Server'), and select 'Properties'. </simpara> <para> + If you want to use the CGI binary, do the following: <itemizedlist> <listitem> <simpara> - ã¤ã³ã¿ã¼ããããµã¼ãã¹ããã¼ã¸ã£ã¼ (MMC) ã«ã¦ãWeb ãµã¤ãã¾ã - ã¯ã¢ããªã±ã¼ã·ã§ã³ã®ã¹ã¿ã¼ãä½ç½®ã¨ãªããã£ã¬ã¯ããªã鏿Wã¦ä¸ - ããã + Under 'Home Directory', 'Virtual Directory', or + 'Directory', click on the 'Configuration' button, + and then enter the App Mappings tab. </simpara> </listitem> <listitem> + <simpara> + Click Add, and in the Executable box, type: + <literal>c:\php\php.exe %s %s</literal> (assuming + that you have unziped PHP in c:\php\). You MUST + have the %s %s on the end, PHP will not function + properly if you fail to do this. + </simpara> + </listitem> + <listitem> <simpara> - ãã®ãã£ã¬ã¯ããªã®ããããã£ã·ã¼ãã(å³ã¯ãªãã¯ãã¦ããã - ããããã£ã鏿ãã¦)ãªã¼ãã³ããã¤ã¥ãã¦ããã¼ã ãã£ã¬ã¯ããªã - ä»®æ³ãã£ã¬ã¯ããªããã£ã¬ã¯ããªã¿ããã¯ãªãã¯ãã¦ä¸ããã + In the Extension box, type the file name extension you want + associated with PHP scripts. Leave 'Method exclusions' + blank, and check the Script engine checkbox. + You must repeat step 3 and 4 for each extension you + want associated with PHP scripts. + (<literal>.php</literal> and <literal>.phtml</literal> + are common.) </simpara> </listitem> <listitem> <simpara> - è¨å®ãã¿ã³ãã¯ãªãã¯ããã¤ã¥ãã¦ãã¢ããªã±ã¼ã·ã§ã³ãããã¿ãã - ã¯ãªãã¯ãã¦ä¸ããã + Set up the appropriate security. (This is done in Internet + Service Manager), and if your NT Server uses NTFS file system, + add execute rights for I_USR_ to the directory that contains + <literal>php.exe</literal>. </simpara> </listitem> + </itemizedlist> + </para> + + <para> + To use the ISAPI module, do the following: + <itemizedlist> <listitem> <simpara> - 追å (Add)ãã¯ãªãã¯ããå®è¡ãã¡ã¤ã«(Executable) ããã¯ã¹ã«ã¦ - 次ã®ããã«å ¥åãã¦ä¸ããã - <literal>c:\path-to-php-dir\php.exe %s %s</literal> - æå¾ã« %s %s ãå¿ ãä»ãã¦ãã ããã - ããããªã㨠PHP ãæ£å¸¸ã«åä½ããªãå¯è½æ§ãããã¾ãã + If you don't want to perform HTTP Authentication using PHP, + you can (and should) skip this step. Under ISAPI Filters, + add a new ISAPI filter. Use PHP as the filter name, and + supply a path to the php4isapi.dll. </simpara> </listitem> <listitem> <simpara> - æ¡å¼µåããã¯ã¹ã«ã¦ãPHP ã¹ã¯ãªããã«é¢é£ä»ããããã¡ã¤ã«æ¡å¼µå - ãå ¥åãã¦ä¸ããã - PHP ã¹ã¯ãªããã«é¢é£ä»ããã忡張å - (é常ã¯ã<literal>.php</literal> 㨠<literal>.phtml</literal> ã§ã) - ãè¨å®ããããã«ãæé 5 ããã³ 6 ãç¹°ãè¿ãã¦ãã ããã + Under 'Home Directory', click on the 'Configuration' button. + Add a new entry to the Application Mappings. Use the path + to the php4isapi.dll as the Executable, supply .php as the + extension, leave Method exclusions blank, and check the + Script engine checkbox. </simpara> </listitem> <listitem> <simpara> - ã»ãã¥ãªãã£ãé©åã«è¨å®ãã¦ä¸ããã(ãã®ä½æ¥ã¯ãã¤ã³ã¿ã¼ãã - ããµã¼ãã¹ããã¼ã¸ã£ã§è¡ãã¾ãã)NT ãµã¼ãã¼ã NTFS ãã¡ã¤ã«ã· - ã¹ãã ã使ç¨ãã¦ããå ´åãI_USR_ ã« <literal>php.exe</literal> - ããããã£ã¬ã¯ããªã®å®è¡æ¨©éãä¸ãã¦ãã ããã + Stop IIS completely </simpara> </listitem> + <listitem> + <simpara> + Start IIS again + </simpara> + </listitem> </itemizedlist> </para> - </sect2> - </sect1> <sect1 id="install.netscape-enterprise"> @@ -3628,8 +3973,8 @@ ã«æé from: bhager@invacare.com - 1. www.sunfreeware.com ã¾ãã¯ä»ã® - ãã¦ã³ãã¼ããµã¤ããã以ä¸ã®ããã±ã¼ã¸ãã¤ã³ã¹ãã¼ã«ãã¦ä¸ãã +1. www.sunfreeware.com ã¾ãã¯ä»ã®ãã¦ã³ãã¼ããµã¤ããã以ä¸ã®ããã±ã¼ + ã¸ãã¤ã³ã¹ãã¼ã«ãã¦ä¸ãã flex-2_5_4a-sol26-sparc-local gcc-2_95_2-sol26-sparc-local @@ -3643,9 +3988,9 @@ mysql-3.23.24-beta (mysql ãµãã¼ãã使ç¨ããå ´å) tar-1.13 (GNU tar) - 2. é©å½ãªãã£ã¬ã¯ããªããã¹ã«å«ã¾ãã¦ãããã©ããã確èªä¸ãã - PATH=.:/usr/local/bin:/usr/sbin:/usr/bin:/usr/ccs/bin - export PATH +2. é©å½ãªãã£ã¬ã¯ããªããã¹ã«å«ã¾ãã¦ãããã©ããã確èªä¸ãã + PATH=.:/usr/local/bin:/usr/sbin:/usr/bin:/usr/ccs/bin + export PATH 3. gunzip php-x.x.x.tar.gz (.gzé å¸ã®å ´åãããã§ãªãå ´åã¯4ã¸é²ã) 4. tar xvf php-x.x.x.tar @@ -3788,9 +4133,97 @@ <simpara> PHPã¨å ±ã«å®è¡ããã忡張æ©è½æ¯ã«æé 2ï½6 ãç¹°ãè¿ãã¾ãã </simpara> + </sect2> + </sect1> + <sect1 id="install.oreilly"> + <title>Oreilly Website Pro Server installs</title> + <para> + This section contains notes and hints specific to Oreilly + Website Pro. + </para> + <sect2 id="install.oreilly.windows"> + <title>Oreilly Website Pro 2.5 and up for Windows</title> + + <simpara> + This list describes how to set up the PHP CGI binary + or the ISAPI module to work with Oreilly Website Pro + on Windows. + </simpara> + + <para> + <itemizedlist> + <listitem> + <para> + Edit the Server Properties and select the tab "Mapping". + </para> + </listitem> + <listitem> + <para> + From the List select "Associations" and enter the desired + extension (".php") and the path to the CGI exe + (ex. c:\php\php.exe) or the ISAPI dll file + (ex. c:\php\sapi\php4isapi.dll). + </para> + </listitem> + <listitem> + <para> + Select "Content Types" add the same extension ".php" + and enter the content type. If you choose the CGI exe + file, enter 'wwwserver/shellcgi', if you chosse the + ISAPI module, enter 'wwwserver/isapi' (both without + quotes). + </para> + </listitem> + </itemizedlist> + </para> </sect2> - + </sect1> + + <sect1 id="install.xitami"> + <title>Xitami Server installs</title> + <para> + This section contains notes and hints specific to Xitami. + </para> + <sect2 id="install.xitami.windows"> + <title>Xitami for Windows</title> + + <simpara> + This list describes how to set up the PHP CGI binary + to work with Xitami on Windows. + </simpara> + + <para> + <itemizedlist> + <listitem> + <para> + Make sure the webserver is running, and point + your browser to xitamis admin console + (usually http://127.0.0.1/admin), and click on + Configuration. + </para> + </listitem> + <listitem> + <para> + Navigate to the Filters, and put the + extension which php should parse (i.e. .php) + into the field File extensions (.xxx). + </para> + </listitem> + <listitem> + <para> + In Filter command or script put the path and name + of your php executable i.e. c:\php\php.exe. + </para> + </listitem> + <listitem> + <para> + Press the 'Save' icon. + </para> + </listitem> + </itemizedlist> + </para> + </sect2> </sect1> <sect1 id="install.otherhttpd"> @@ -3800,6 +4233,8 @@ ãããµã¼ãã¼ã«é¢ä¿ããè¨å®ãªãã·ã§ã³ã®å®å ¨ãªãªã¹ãã«ã¤ãã¦ã¯ã <link linkend="install.configure.servers">ãµã¼ãã¼ã«é¢ä¿ãã ãªãã·ã§ã³</link> ãåç §ä¸ããã + The PHP CGI binaries are compatible with almost all + webservers supporting the CGI interface. </para> </sect1> @@ -3855,16 +4290,17 @@ <title>å½éå颿°ã«ã¤ãã¦</title> <simpara> - å½éå颿°ãæå¹ã«ãããã¨ã«ãããæ¥æ¬èªå¦çæã®æ¼¢åã³ã¼ãèªå夿æ©è½ã - å§ãã¨ããæç¨ãªæ©è½ãå©ç¨å¯è½ã«ãªãã¾ãã + å½éå颿°ãæå¹ã«ãããã¨ã«ãããæ¥æ¬èªå¦çæã®æ¼¢åã³ã¼ãèªåå¤ + ææ©è½ãå§ãã¨ããæç¨ãªæ©è½ãå©ç¨å¯è½ã«ãªãã¾ãã(å½éåçã®PHP + ã®ã¿å¯¾å¿) </simpara> <sect3 id="i18n-abstract"> <title>å½éå颿°ã®å ¥æ</title> <para> - PHP å½éåããã±ã¼ã¸ã¯ããPHP3å½éåãã¼ã ãã«ããç¾å¨ãã¹ãä¸ã§ã - <ulink url="http://www.happysize.co.jp/techie/php-ja-jp/"> - http://www.happysize.co.jp/techie/php-ja-jp/</ulink> + PHP å½éåããã±ã¼ã¸ã¯ããPHPå½éåããã¸ã§ã¯ããã«ããéçºããã + <ulink url="http://php.jpnnet.com/"> + http://php.jpnnet.com/</ulink> ã¾ã㯠<ulink url="ftp://ftp.happysize.co.jp/php-ja-jp/"> ftp://ftp.happysize.co.jp/php-ja-jp/</ulink>ã§æã«å ¥ãã¾ãã