CVS update: php3

Date: Monday June 28, 1999 @ 20:17 Author: jim Update of /repository/php3 In directory php:/tmp/cvs-serv5049 Modified Files: README.WIN32 Log Message: Update Windows build instructions. Index: php3/README.WIN32 diff -u php3/README.WIN32:1.4 php3/README.WIN32:1.5 --- php3/README.WIN32:1.4 Mon Jun 21 19:49:19 1999 +++ php3/README.WIN32 Mon Jun 28 20:17:57 1999 @@ -5,56 +5,64 @@ --------------------------------------------------------------------- COMPILING UNDER WINDOWS -Windows compilation has only been tested with Microsoft Visual C++ +Windows compilation has only been tested with Microsoft Visual C++ Version 6 Professional Edition. The PHP executable has only had limited -testing under Windows 95. SAFE MODE and any User or Group functionality -is not available. +testing under Windows 95 and Windows 98. Safe mode and many filesystem- +related functions are not available under Windows. ----------------------------------------------------------------------- +Obtaining the Support Files + +To compile PHP and all of the extensions supported in the default +configuration, you will need to obtain the necessary support programs +(bison and flex) and include files and libraries. Simply download +http://www.php.net/extra/win32build.zip and unzip it in the win32 +directory of the source. (This should create bin, include, and lib +directories under win32. You may need to specify a flag such as "-d" +to your unzip program to make it unpack the files correctly.) + +It may also be possible to use pre-installed versions of flex and +bison, but you will need to change the custom build instructions +in the php_custom_build project. + +----------------------------------------------------------------------- Compiling PHP with MSVC6 -There are three msvc workspaces provided with this distribution. The one -most people will use is php3.dsw. This contains project files for two -versions on PHP, one with mySQL compiled internaly, and one without (both -have ODBC internaly compiled). It also contains all the modules. +There are two MSVC workspaces provided with this distribution. The one +most people will use is php3.dsw. This contains project files for the CGI +version of PHP, along with a number of dynamically loadable extensions. The next workspace is php3extras.dsw. This project contains the converter and a program called phpwatch, which is a simple program to watch debugger -output under windows. The 'socket' program is also available from the php +output under Windows. The 'socket' program is also available from the PHP site, which is a better alternative to phpwatch. ------------------------------------------------------------------------ -Base Configuration and Configuration Issues - -*The base configuration for the windows php version contains odbc - support. Support for other database modules will be provided as external dll files. -*ODBC can be used to connect to many of the databases previously -supported by php (though they can still be compiled in if you have -the libraries!) - ------------------------------------------------------------------------ -Makefiles - -Be sure to edit any windows makefile and change the include directories -to be appropriate for your system. - ----------------------------------------------------------------------- -CGI Version - -The makefile for the cgi version of php is located in the win32 -subdirectory of the php source tree. This make file is specificaly -for Visual C++ V5. - ------------------------------------------------------------------------ -ISAPI/NSAPI/WSAPI/Apache Versions - -These versions are not yet working. They are located in the php3sapi.dsw -workspace. - - ------------------------------------------------------------------------ -Other Libraries - -See the php faq at php.net for information on where to obtain the various -libraries needed to compile some modules. +Default Configuration and Configuration Issues +* The default configuration for the Windows PHP version contains ODBC + support. Support for other database modules is provided using + dynamically-loaded extensions. + +* ODBC can be used to connect to many of the databases that are also + supported using specific extensions. + +----------------------------------------------------------------------- +Working with the Project Files + +There are some things to remember when working with the project files: + +1. Do not include system-specific paths. All paths should be relative + to the project files (which are in the win32\ directory). You should + install Windows-specific header files and libraries in the include\ + and lib\ directories and update win32build.zip. + +2. Extensions should output their DLL into the module_{debug,release} + directories, and intermediate objects into module_{debug,release}\ext + (where ext is a unique name for the extension). This avoids having + collisions when two extensions compile the same file. (For example, + the Solid extension simply compiled unified_odbc.c with some Solid- + specific #defines. Without writing the intermediate objects to a + unique subdirectory, DevStudio will get confused when it tries to + compile another extension that also compiles unified_odbc.c with + different #defines.