标签 PECL 下的文章

Build PHP Binary from Source: Step 2 – with PECL extensions

PECL (PHP Extension Community Library) is conceptually very similar to PEAR. PECL contains C extensions for compiling into PHP. As C programs, PECL extensions run more efficiently than PEAR packages. If you follow the following procedure, you can build PECL extensions together with the PHP binary package.

I. Prerequisite: You must finish the Build PHP Binary with the default modules successfully.

II. Download the PECL source code:

  1. My example is trying to compile the xdebug and APC extensions.
    1. xdebug: Download it at http://pecl.php.net/package/xdebug
    2. APC: Download it at http://pecl.php.net/package/APC
  2. Unzip the downloaded zip files and put them under C:\php-sdk\php54dev\vc9\x86\pecl. They will look like the following screenshots:

III. Compile:

  1. Set the environment: Open the “Windows SDK 6.1 Shell” (it’s available from the start menu group) and execute the following commands in it. If you are using 64 bit system, don't try to change the parameter to /x64, otherwise during the make period, you will see tons of WARNING.
    set PATH=D:\php-sdk\bin;%PATH%
    setenv /x86 /xp /release
    cd c:\php-sdk\
    bin\phpsdk_setvars.bat

    You will get the following screen:
  2. Build the configuration file for creating the make file:
    cd C:\php-sdk\php54dev\vc9\x86\php-5.4.5-src
    buildconf

    If you get an error like:
    Input Error: There is no script engine for file extension ".js".


    You need to edit the buildconf.bat file as below:

    Run the buildconf again:
    buildconf

    You will get the following screen:

    A new configuration file: configure.js will be created as below:

    Now, you can check the configuration options:
    configure --help

    If you get the following error again:
    Input Error: There is no script engine for file extension ".js".

    Please edit the configure.bat file and add /e:jscript after the /nologo.

    Run the configure --help again:
    configure --help

    If you installed the Cygwin, you can use the following commands to check if the APC and xdebug are included in the configuration file:
    configure --help | grep apc
    configure --help | grep xdebug

    If the APC and xdebug are included, you will see the following screen:
  3. Create the make file:
    configure --disable-snapshot-build --disable-debug-pack --disable-ipv6 --disable-zts --disable-isapi --disable-nsapi --without-t1lib --without-mssql --without-pdo-mssql --without-pi3web --without-enchant --enable-com-dotnet --with-mcrypt=static --disable-static-analyze --with-xdebug=shared --enable-apc

    If you run it successfully, you will see the screen as below. Pls check if the apc and xdebug extensions are included:
  4. Make the binary package by typing nmake:
    nmake

    Wait for a while, if you see this result, you succeeded.

    You will also find a new "Release" directory appeared under C:\php-sdk\php54dev\vc9\x86\php-5.4.5-src as below. If you see the php_xdebug.dll, it means the xdebug DLL has been created.

    Check the module:
    C:\php-sdk\php54dev\vc9\x86\php-5.4.5-src\Release\php.exe -m

    If you can see the apc in the screen as below, it means the apc module was compiled successfully in the PHP binary:

Congratulations! You are all done!

Build PHP Binary from Source: Step 1 - with the Default Modules

This 1st step will prove your environment setup is correct. Make sure you can finish this step successfully before going to the 2nd step.

I. Environment and related Packages:

  1. Microsoft Visual C++ 2008 Express Edition with SP1:
    1. Another name is MSVC9. Download it at http://www.microsoft.com/visualstudio/en-us/products/2008-editions/express
    2. The recent PHP binary packages are compiled in MSVC9 environment. This tutorial is for MSVC9. Please don't use the Microsoft Visual C++ 2010 or later, which will not be compatible with the current PHP Windows Binaries.
    3. If you want MSVC6 environment, you need to install the Microsoft Visual C++ 6.0 and Windows Server 2003 SP1 Platform SDK at http://www.microsoft.com/en-us/download/details.aspx?id=6510
  2. Windows SDK 6.1:
    1. You must use the Windows SDK instead of the SDK included in above MSVC9. For building PHP5.3, you need to use Windows SDK 6.1 (Windows SDK for Windows Server 2008 and .NET Framework 3.5, http://www.microsoft.com/en-us/download/details.aspx?id=11310#Overview). For more information regarding the SDK, please seehttps://wiki.php.net/internals/windows/windowssdk
  3. PHP SDK Binary Tools:
    1. Download a zip file from http://windows.php.net/downloads/php-sdk/. What I downloaded on 8/7/2012 was php-sdk-binary-tools-20110915.zip
    2. Unzip it, rename and move the folder to C drive. The file structure will look like the following screenshot:
  4. Dependable libs:
    1. Download a zip file from http://windows.php.net/downloads/php-sdk/. What I downloaded was deps-5.4-vc9-x86.7z on 8/3/2012.
    2. Create directory tree like: C:\php-sdk\php54dev\vc9\x86
    3. Unzip the zip file and move the deps directory under C:\php-sdk\php54dev\vc9\x86. So, it will be like the following screenshot:
  5. PHP5.4 Sources:
    1. Download the source code from http://windows.php.net/download/ (click the "Download source code" link)
    2. After unzip move it under C:\php-sdk\php54dev\vc9\x86\, You can name this folder to what you like. Mine is as below:

      Now you are ready to compile!

II. Compile:

  1. Set the environment: Open the “Windows SDK 6.1 Shell” (it’s available from the start menu group) and execute the following commands in it. If you are using 64 bit system, don't try to change the parameter to /x64, otherwise during the make period, you will see tons of WARNING.
    set PATH=D:\php-sdk\bin;%PATH%
    setenv /x86 /xp /release
    cd c:\php-sdk\
    bin\phpsdk_setvars.bat

    You will get the following screen:
  2. Build the configuration file for creating the make file:
    cd C:\php-sdk\php54dev\vc9\x86\php-5.4.5-src
    buildconf

    If you get an error like:
    Input Error: There is no script engine for file extension ".js".


    You need to edit the buildconf.bat file as below:

    Run the buildconf again:
    buildconf

    You will get the following screen:

    A new configuration file: configure.js will be created as below:

    Now, you can check the configuration options:
    configure --help

    If you get the following error again:
    Input Error: There is no script engine for file extension ".js".

    Please edit the configure.bat file and add /e:jscript after the /nologo.

    Run the configure --help again:
    configure --help

    If you can get the following screen, it means you successfully created the configuration file:
  3. Create the make file:
    configure --disable-snapshot-build --disable-debug-pack --disable-ipv6 --disable-zts --disable-isapi --disable-nsapi --without-t1lib --without-mssql --without-pdo-mssql --without-pi3web --without-enchant --enable-com-dotnet --with-mcrypt=static --disable-static-analyze

    If you run it successfully, you will see the screen as below:

  4. Make the binary package by typing nmake:
    nmake

    Wait for a while, if you see this result, you succeeded.

    You will also find a new "Release" directory appeared under C:\php-sdk\php54dev\vc9\x86\php-5.4.5-src as below:
  5. Test the PHP Binary files:
    # Check PHP Version
    C:\php-sdk\php54dev\vc9\x86\php-5.4.5-src\Release\php.exe -v
    # It is same to phpinfo()
    C:\php-sdk\php54dev\vc9\x86\php-5.4.5-src\Release\php.exe -i
    # Check PHP modules
    C:\php-sdk\php54dev\vc9\x86\php-5.4.5-src\Release\php.exe -m
    

    If you can get the results properly, you are all done!