PHP Extension Development Introductory Tutorial _php Tutorial

Introduction to PHP Extension Development tutorial

This article mainly introduces the PHP extension Development Primer Tutorial, this article explains the use of C language in the Linux system to develop a PHP extension should have the most basic knowledge, the need for friends can refer to the following

PHP Extension Development

I'm going to summarize my learning and understanding of PHP Extension Development in this series, trying to simply and clearly describe the basics of developing a PHP extension in a Linux system. The level is low, inevitably has the mistake, hoped to point out.

Preparatory work

Start by getting a copy of the PHP source code (you can check it out on GitHub, or download the latest stable version on the official website) and compile it. To speed up the compilation, we recommend disabling all additional extensions (using the--disable-all option), but it's a good idea to turn on debug (using the--enable-debug option) and thread safety (using--ENABLE-MAINTAINER-ZTS). However, to turn off debug when publishing the extension, choose whether to turn on thread safety as appropriate:

The code is as follows:

$./buildconf--force
$./configure--disable-all--enable-debug--enable-maintainer-zts
$ make

Note that we did not specify the--prefix option (and also no make install), because this is not required. Note that if you look at the output information, you may need to install some dependent packages to successfully compile PHP.

Compiled PHP executable program in the source code of the SAPI directory, corresponding to different host environments have different subdirectories, we will use the CLI (Command line interface) environment, we can build an alias for easy reference:

The code is as follows:

$ alias php-dev=/usr/local/src/php-5.6.5/sapi/cli/php

There are a few command-line options that are useful:

The code is as follows:

PHP-DEV-H # Printing Help information
PHP-DEV-V # Print version information
Php-dev--ini # Print configuration information
PHP-DEV-M # Print Loaded module information
Php-dev-i # Phpinfo
Php-dev-r # Execute Code

Extended skeleton

All the official extensions of PHP are in the Ext directory of the source code, and the extensions we write ourselves can be placed in that directory. Note that this directory has a shell script named Ext_skel, which is used to generate the PHP extension skeleton, which can help us to quickly create a PHP extension:

The code is as follows:

$./ext_skel--extname=myext

The above command helped us create an extension called Myext, the source code in the Myext directory. Execution of the script without any parameters can print help information so that you can see more options available to the script.

Next, let's finish our expansion. Go to the Myext directory, edit the CONFIG.M4 configuration file, find the Php_arg_enable macro function, and remove the previous DNL comment (three lines). Return to the source root and re-execute the buildconf, configure, and make commands:

The code is as follows:

$./buildconf--force
$./configure--help | grep myext
--enable-myext Enable Myext Support
$./configure--disable-all--enable-myext--enable-debug--enable-maintainer-zts
$ make

Note that we use the./configure--help | grep Myext Prints the loading of our extensions, and if we don't see the output below, our extension is not configured successfully, and we look back at the config.m4 file.

This compilation should be very fast because most of the code has already been compiled. PHP has another way of compiling extensions (using dynamic connections to compile extensions into. so files), but we recommend using static compilation when developing extensions, because this eliminates the step of loading extensions in the configuration file.

If all goes well, our first extension is ready for execution:

The code is as follows:

$ php-dev-m | grep myext
Myext
$ Php-dev-r ' echo confirm_myext_compiled ("Myext"). "\ n";
congratulations! You have successfully modified EXT/MYEXT/CONFIG.M4. Module Myext is now compiled to PHP.

The first command shows that our extension has been loaded. The second command executes the function that the Ext_skel extension skeleton automatically created for us. Of course, this function is meaningless, but we can easily adapt this function to Hello World.

Create an extension manually

Most tutorials are developed with the Ext_skel extension skeleton as a prototype, which is of course convenient and quick. But I personally prefer a purely manual way of developing extensions, because it's easier to understand every detail.

To create an extension manually, first go to the EXT directory and create our extension directory myext2. There are several files that are required: config.m4,myext2.c and php_myext2.h.

First, let's write the configuration file config.m4:

The code is as follows:

Php_arg_enable (MYEXT2, whether to ENABLE myext2 support,
[--ENABLE-MYEXT2 enable MYEXT2 support])

if test "php_myext2"! = "no"; Then
Php_new_extension (Myext2, myext2.c, $ext _shared)
Fi

CONFIG.M4 is actually the configuration file used by the autoconf program, autoconf is an important component in the Autotools Toolbox. It takes a long time to fully introduce the usage of autoconf, but the usage here is very simple.

Php_arg_enable is a macro function defined by PHP for autoconf, MYEXT2 is its first parameter, which indicates the name of the extension, and the next two parameters are only used to display when make and configure are executed, so we can write it casually. [] In the autoconf syntax, the function is similar to double quotation marks, used to wrap a string (note that the second argument contains a space, but you can use no square brackets). There is also a fourth parameter to indicate whether the extension is on or off by default (yes or no) and no by default.

The following three lines are actually shell syntax, to determine whether we have opened the PHP_MYEXT2 extension module. If the extension (--ENABLE-MYEXT2) is turned on, the value of the $PHP_MYEXT2 variable is not no, so the Php_new_extension macro is executed. This macro function is also the extension syntax defined by PHP for autoconf, the first parameter is also the extension name, the second parameter is the extension to compile the C file, if there are more than one, then write down (space delimited), the third parameter is fixed is $ext_shared.

Next write the php_myext2.h header file, the name of the file is the PHP extension specification-php_ extension. h:

The code is as follows:

#ifndef Php_myext2_h
#define Php_myext2_h

extern zend_module_entry Myext2_module_entry;
#define PHPEXT_MYEXT2_PTR &myext2_module_entry

#define Php_myext2_version "0.1.0"

/* Prototypes */
Php_function (hello);

#endif/* Php_myext2_h */

The main code here is to define a macro named Phpext_myext2_ptr, which is referenced by the PHP bottom to refer to our extensions. As you can see, the name of the macro is also the canonical-phpext_ extension _ptr. And Myext2_module_entry is the struct that we will define later in the. c file, and its name is also canonical-extension _module_entry.

We also define a macro that identifies our extension version number and a function prototype (through the Php_function macro, the parameters of the Php_function macro function are externally available function names), which we will implement later.

Finally, consider the implementation of the myext2.c file:

The code is as follows:

#include "Php.h"
#include "Php_myext2.h"

/* {{myext2_functions[]
*
* Every user visible function must has a entry in myext2_functions[].
*/
static const Zend_function_entry myext2_functions[] = {
Php_fe (Hello, NULL)
Php_fe_end
};
/* }}} */

/* {{{myext2_module_entry
*/
Zend_module_entry Myext2_module_entry = {
Standard_module_header,
"Myext2",/* Module name */
Myext2_functions,/* Module functions */
NULL,/* Module Initialize */
NULL,/* Module shutdown */
NULL,/* Request Initialize */
NULL,/* Request shutdown */
NULL,/* phpinfo */
Php_myext2_version,/* Module VERSION */
Standard_module_properties
};
/* }}} */

#ifdef COMPILE_DL_MYEXT2
Zend_get_module (MYEXT2)
#endif

/* {{{proto void Hello ()
Print "Hello world!" */
Php_function (Hello)
{
php_printf ("Hello world!\n");
}
/* }}} */

In contrast to the. c files created by the extended skeleton, we will find that our. c files are very simple, but they are enough for a basic extension.

The code above is simple and clear, and most of the comments are already very descriptive. Let us briefly summarize the following:

1. Start with the header file that we want to use. Php.h is a must, it has helped us to include the vast majority of the standard library files we will use, such as stdio.h,stdlib.h and so on.
2.myext2_functions defines an array of structures that are composed of the functions we want to expose, each of which is specified by a PHP_FE macro. The PHP_FE macro has two parameters, the first is the function name that can be used externally, the second is the parameter information (here we simply use NULL), and the last element must be php_fe_end. Note its comments, emphasizing again that each function to be exposed to external use must be defined in the struct array.
3.myext2_module_entry defines our module information, which is a struct, and most of the properties have been explained by comments. Note that the middle of the five function pointers, we are simply set to NULL, in the subsequent blog post will tell their usage.
The 4.zend_get_module (MYEXT2) macro function is contained by a IFDEF macro, so it is determined whether it is invoked as appropriate. As to what circumstances will be invoked, what will not be called, in subsequent blog post will be narrated.
5. The last few lines of code we implemented the Hello function, it is very simple, call php_printf output Hello world! followed by a newline character, php_printf usage and printf exactly the same.
6. {{{and}}} in the comments is used to facilitate the folding of vim and other editors, we recommend that you also write comments.
This involves a number of macros, such as Php_fe,php_fe_end,php_function, and so on, the full introduction of these macros to follow the blog post can, the simplest way is to remember these macros.

Notice that the naming of each of our files, the naming of the variables, the spaces and indents, and the annotations are all very canonical, and following these specifications, we can make the code we write more in line with the code of PHP itself, and we recommend that you use such a specification to develop PHP extensions.

Finally, compile and run our extension:

The code is as follows:

$./buildconf--force
$./configure--help | grep myext2
--ENABLE-MYEXT2 Enable MYEXT2 Support
$./configure--disable-all--enable-myext2--enable-debug--enable-maintainer-zts
$ make

$ php-dev-m | grep myext2
Myext2
$ Php-dev-r ' Hello (); '
Hello world!

http://www.bkjia.com/PHPjc/961082.html www.bkjia.com true http://www.bkjia.com/PHPjc/961082.html techarticle PHP Extension Development Introductory Tutorial This article mainly introduces the PHP extension Development Primer Tutorial, this article explains the use of C language in the Linux system to develop a PHP extension should have the most basic knowledge, need ...

