在编译期间检测是否正在使用给定扩展名编译PHP

Question

I am trying to build an extension for PHP. After following Sara Golemon's book I have a basic extension which I can compile as a shared module and, in addition, I can compile it statically along PHP itself.

Now I want to modify the PHP interpreter in order to intercept particular internal function invocations and communicate these calls to my extension. I want to do this only when my extension is statically compiled with PHP---the interpreter build process should otherwise generate an unmodified PHP binary. My understanding is that I should use the C preprocessor. However, to achieve my goal I need a preprocessor flag that will only be raised when PHP is configured to compile with my extension (ie ./configure --enable-myextension). Unfortunately, I cannot find such a flag nor one seems to be set by the configure script.

I should say here that I have tried setting preprossessor flags within my extension's code but this will not work. My extension is first touched late in the build process (ie roughly after the core of the interpreter) and the flags I set there are not active when the bulk of interpreter code is being compiled.

Any thoughts? Do the above sound reasonable?

Answer 1

My understanding is that I should use the C preprocessor.

Nope, you don't need that.

I need a preprocessor flag that will only be raised when PHP is configured to compile with my extension

Why would you want that? It would basically limit the functionality of your extension artificially, although it's possible to hook function calls no matter how your extension is compiled.

Do the above sound reasonable?

In my opinion, it's not reasonable. Please have a look at how AOP hooks function calls: https://github.com/AOP-PHP/AOP

If you need to hook more than just function calls, you need to reach down at the lowest level, the opcodes, by using zend_set_user_opcode_handler() . Please use lxr.php.net or similar tools (fgrep, etc) to find out where and how such handlers are used. I know laruence was working hard on an interesting extension last year here: http://svn.php.net/viewvc/pecl/taint/trunk/taint.c?view=markup so I would take that as the most "up to date" way of doing things as a reference, if anything has changed in the meanwhile.