#2 · closed · 4 comments
I've pushed this up so that others can see what I have been doing so far. The objective of the current work is to create a minimum changes CLI version that works -- at least intermittently on my dev (Ubuntu 64bit) laptop. I will document what I am doing more fully in the Wiki as I go along. This version runs the PHP and Zend test suite -- albeit with known problems and significant caveats. It is a development vehicle only.
Thanks Terry. Just to make sure I understand correctly: - is this to be used only as CLI or can it be compiled into an .so to be run with Apache? - does it support file-based storage for the opcode cache to be run in a suPHP environment? If yes, are there any extra/changed ini settings? Cheers
Both of these Qs essentially have the same answer, as this fork essentially extends Opcache functionality, it can still be configured and built with the mod-php and gci variants. It contains -- or will contain -- a lot of built in test diagnostics (see the debug header for the ENTER and DEBUGx macros) which I use to augment gdb work, though if debug isn't enabled, then these generate null strings. suPHP -- which a terribly inefficient bit of S/W BTW -- runs the php GCI image. I've not done this work and won't until I've sorted the basic bugs in a CLI environment, though from my LPC experience its mainly a re config and make. Please hang-fire until I've documented this stuff properly in the wiki, rather than thi thread :-)
@normadize, I have started adding the Wiki material. :-)
The Wiki content now reflects the dev-filecache branch, which is now on a path to an alpha production version. I am now closing this issue.