PHPCPP安裝以及hello world

aa楊發表於2019-02-16
PHP

學習了一段時間做PHP擴充套件開發，由於C的難度較大，記憶體回收，指標每一個都可以能讓初學者望而卻步，加上C開發效率太低，小型企業對於這種高大上的開發，還是少觸碰為好。但是有時候PHP開發執行效率確實太低，而且存在很大的資源浪費，並且這個又是無法避免的（比如excel），混合開發讓專案的遷移和可維護性都降低了。

一次偶然機會發現了PHPCPP，C++開發PHP的擴充套件，C++不用說了吧！執行效率最接近C的語言。最主要的是PHPCPP大大的降低了PHP擴充套件的開發難度。以前開發擴充套件，初始化專案對於小白來說都可能是個災難，而PHPCPP對於希望開發擴充套件的PHPER可以說是一個福音。

在不接觸PHP底層的情況下，採用PHPCPP是一個很好的選擇方案。下面廢話不多說，上乾貨。

首先選擇一個你常用的linux版本，然後下載PHPCPP

 git clone https://github.com/CopernicaMarketingSoftware/PHP-CPP.git

然後編譯並安裝PHPCPP

make &&sudo  make install

這樣PHPCPP就安裝成功了。

從PHPCPP下載一個空專案http://www.php-cpp.com/EmptyE…

這裡說明一下，預設最新PHPCPP是隻支援PHP7的，如果需要支援PHP5.X需要下載他的另外一個版本，API一樣，只是sdk不同，所以採用PHPCPP開發的擴充套件原始碼是相通的，只是需要在對應版本編譯。

言歸正傳，空專案中的Makefile，可以修改NAME，這個是你的擴充套件檔名稱，其他都保持不變

#
#   Makefile template
#
#   This is an example Makefile that can be used by anyone who is building
#   his or her own PHP extensions using the PHP-CPP library. 
#
#   In the top part of this file we have included variables that can be
#   altered to fit your configuration, near the bottom the instructions and
#   dependencies for the compiler are defined. The deeper you get into this
#   file, the less likely it is that you will have to change anything in it.
#

#
#   Name of your extension
#
#   This is the name of your extension. Based on this extension name, the
#   name of the library file (name.so) and the name of the config file (name.ini)
#   are automatically generated
#

NAME                =   yourextension

#
#   Php.ini directories
#
#   In the past, PHP used a single php.ini configuration file. Today, most
#   PHP installations use a conf.d directory that holds a set of config files,
#   one for each extension. Use this variable to specify this directory.
#
#   In Ubuntu 14.04 Apache 2.4 is used, which uses the mods-available directory
#   instead of a conf.d directory. In 16.04 the directory changed yet again.
#   This has to be checked.
#

UBUNTU_MAJOR  := $(shell /usr/bin/lsb_release -r -s | cut -f1 -d.)
OVER_SIXTEEN  := $(shell echo "${UBUNTU_MAJOR} >= 16" | bc)
OVER_FOURTEEN := $(shell echo "${UBUNTU_MAJOR} >= 14" | bc)

ifeq (${OVER_SIXTEEN}, 1)
    INI_DIR     =   /etc/php/7.0/mods-available/
else ifeq (${OVER_FOURTEEN}, 1)
    INI_DIR     =   /etc/php5/mods-available/
else
    INI_DIR     =   /etc/php5/conf.d/
endif

#
#   The extension dirs
#
#   This is normally a directory like /usr/lib/php5/20121221 (based on the 
#   PHP version that you use. We make use of the command line `php-config` 
#   instruction to find out what the extension directory is, you can override
#   this with a different fixed directory
#

EXTENSION_DIR       =   $(shell php-config --extension-dir)

#
#   The name of the extension and the name of the .ini file
#
#   These two variables are based on the name of the extension. We simply add
#   a certain extension to them (.so or .ini)
#

EXTENSION           =   ${NAME}.so
INI                 =   ${NAME}.ini

#
#   Compiler
#
#   By default, the GNU C++ compiler is used. If you want to use a different
#   compiler, you can change that here. You can change this for both the 
#   compiler (the program that turns the c++ files into object files) and for
#   the linker (the program that links all object files into the single .so
#   library file. By default, g++ (the GNU C++ compiler) is used for both.
#

COMPILER            =   g++
LINKER              =   g++

#
#   Compiler and linker flags
#
#   This variable holds the flags that are passed to the compiler. By default, 
#   we include the -O2 flag. This flag tells the compiler to optimize the code, 
#   but it makes debugging more difficult. So if you`re debugging your application, 
#   you probably want to remove this -O2 flag. At the same time, you can then 
#   add the -g flag to instruct the compiler to include debug information in
#   the library (but this will make the final libphpcpp.so file much bigger, so
#   you want to leave that flag out on production servers).
#
#   If your extension depends on other libraries (and it does at least depend on
#   one: the PHP-CPP library), you should update the LINKER_DEPENDENCIES variable
#   with a list of all flags that should be passed to the linker.
#

COMPILER_FLAGS      =   -Wall -c -O2 -std=c++11 -fpic -o
LINKER_FLAGS        =   -shared
LINKER_DEPENDENCIES =   -lphpcpp

#
#   Command to remove files, copy files and create directories.
#
#   I`ve never encountered a *nix environment in which these commands do not work. 
#   So you can probably leave this as it is
#

RM                  =   rm -f
CP                  =   cp -f
MKDIR               =   mkdir -p

#
#   All source files are simply all *.cpp files found in the current directory
#
#   A built-in Makefile macro is used to scan the current directory and find 
#   all source files. The object files are all compiled versions of the source
#   file, with the .cpp extension being replaced by .o.
#

SOURCES             =   $(wildcard *.cpp)
OBJECTS             =   $(SOURCES:%.cpp=%.o)

#
#   From here the build instructions start
#

all:                    ${OBJECTS} ${EXTENSION}

${EXTENSION}:           ${OBJECTS}
                        ${LINKER} ${LINKER_FLAGS} -o $@ ${OBJECTS} ${LINKER_DEPENDENCIES}

${OBJECTS}:
                        ${COMPILER} ${COMPILER_FLAGS} $@ ${@:%.o=%.cpp}

install:        
                        ${CP} ${EXTENSION} ${EXTENSION_DIR}
                        ${CP} ${INI} ${INI_DIR}

clean:
                        ${RM} ${EXTENSION} ${OBJECTS}
main.c原始碼


#include <phpcpp.h>
#include <iostream>

void myFunction()
{
    Php::out << "hello world" << std::endl;
}

extern "C" {
    PHPCPP_EXPORT void *get_module() {
        static Php::Extension extension("my_extension", "1.0");
        extension.add<myFunction>("myFunction");
        return extension;
    }
}

這樣一個擴充套件程式碼就完成了，執行編譯

make
然後將生成的xxx.so拷貝到PHP擴充套件目錄，並在PHP.INI加入
extension=yourextension.so

執行php -m檢視是否載入了擴充套件，如果已經成功載入那麼，就會顯示my_extension在裡面了

php  -m

那麼PHP中如何呼叫呢？如果沒有使用名稱空間那麼可以這樣

<?php
   myFunction();

如果使用了需要加上

<?php
 myFunction();

這樣第一個擴充套件就完成了。

以後會每週至少更新兩篇關於PHPCPP的文章記錄並分享自己的使用PHPCPP的開發經驗。

相關文章