why do you have to compile php (shared object) extensions?

[geekpie]

Why do you compile php shared object extensions? 

 

Let's say I want to add "extname":  the normal process is:

 

cd extname

$ phpize

$ ./configure && make

 

which creates a .so file (extname.so)

 

Why don't I just download a .so file, put it in place and enable it in php.ini ?

[trq]

Good question, I'm no expert but have compiled a few shared objects in my time. I believe the reason these need to be compiled on the actual machine is to enable them to link into the underlying libraries that they use as well as php itself.

[geekpie]

could be right:  but you (in my experience) never seem to have tell the configure command anything (such as the location of local libraries).

[rhodesa]

to my knowledge it's because every version of linux is different in one form or another. so, it needs the original source code to compile a version for itself. you could distribute the so, but it would only be good for that particular version of linux. since there are so many linux variations out there, it's easier to just supply the source, and have the user compile it.

[trq]

could be right:  but you (in my experience) never seem to have tell the configure command anything (such as the location of local libraries).

 

Default locations are searched and the libraries usually found. Most libs have a .configure option enabling you to point php to a specific location if need be.