Re: Re: playing with inline_C

On Sunday, October 20, 2002, at 10:10 PM, Alan Knowles wrote:

George Schlossnagle wrote:

Hi Alan, I'm afraid I don't understand your comments regarding the pear installer - I'm not very familiar with how it works. Can you be more descriptive about what the changes would be and how they would benefit things?

Its probably worth looking at the code in PEAR/Builder.php, this takes a php extension sources, run phpize, ./configure and make/make install (and does have some support for windows extension building if you have msdev) It may be worth looking into utilizing this..

Ahh... yes. That would be beneficial. I will look into that. If I read the end of your mail correctly and you're interested in doing some of that, that would be really cool as well.

Regarding your other points:

a) Is it really neccessary to use Inline_C.php.in, just using a instantator, or factory method seems a little nicer.. $ic = new Inline_C('/path/to/ext.dir/');

The reason for this is because I wanted it to 'just work'. I'm happy with overriding the builddir during instantiation, but having a default is nice. That way if I have Inline_C installed, my scripts that use it are portable between architectures (and portable for distribution as well). Especially since there is already setup that needs to be done (building the build tree), doing a bit of module configuration seems ok to me. If you have a better solution, I'm all ears.

The idea was to just build a standard extension set of files (eg. config.m4,x.c,php_x.h)- and run PEAR::builder, this will be alot slower on the first build, but would hopefully allow Inline_C or an extended version to replace the ext_skel script..., with something a bit more powerfull.

Yes, makes sense.

c) when running makebuildtree.head on the php head (probably a few month old), I get configure: error: can not find sources in . or ..

I'm not sure when the 'new' build system went in. Can you try with mkbuildtree.4.2.3? Also, you are running it with an absolute path to your builddir, right? That's key.

Will have another play later :) regards Alan

d) can you add an optional argument to ->compiler($extensionname), so you can hard code an extension name, rather than getting an md5 one?

Sure.

If you dont mind me hacking away on it (and the pear installer), just give us a nod :)

Please go wild.

Regards Alan // George Schlossnagle

// Principal Consultant

// OmniTI, Inc          http://www.omniti.com

// (c) 240.460.5234 (e) george@omniti.com // 1024D/1100A5A0 1370 F70A 9365 96C9 2F5E 56C2 B2B9 262F 1100 A5A0