Hi!
Its coming with it's own ./configure. I think you can hang one
I'd suspect most of what it's configure is doing is done by the php one too, and the rest can be converted to PHP's configure fragment. The thing is that if you want to have it in PHP tree, it won't look too good for it to have its own configure, no other SAPI does that and there's no reason to. As for bundling libevent, I have no idea if BSD code can be put in php tree... It'd be much nicer if these chanegs were merged into libevent - it seems to be pretty alive, 3 releases this year.
yet. But once the Makefile is created, then make-stage is like an automatic recursion thing isn't it?
If you do it by PHP standards, it is, but otherwise I don't know - let configure gurus on the list speak about it.
file). They said nothing about requiring to share the same build command. I mention this because it didn't represent any kind of technical issue for making a debian package. Indeed it seemed easier not to.
Well, PHP has certain rules and customs of how SAPIs are built. Of course, you can take PHP code and do whatever you like with it (if you not call the result PHP without permission :) but if it's going to be inside PHP tree then it should be organized by PHP rules. Otherwise PHP tree would be an incomprehensible mess.
-- Stanislav Malyshev, Zend Software Architect s...@zend.com http://www.zend.com/ (408)253-8829 MSN: s...@zend.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
