Alec wrote: > I actually wrote that. I never imagined someone would actually find > that useful! > > If you don't mind having a few external dlls, you can use dl (ick!) to > load the extensions. > > I gave up supporting that because compiling the custom lightweight > stubs took more work than I cared for. I am considering reviving the > project and this time not writing in PHP (PHP should really not be > used for GUIs IMO).
I have given a look at http://winbinder.org/forum/viewtopic.php?f=10&t=1178 Your usage of php.exe and php5ts.dll in the stub folder confused me, but I guess that it is there just for being able to debug with that stub, and actually never used. Your current approach for a stub (set of php + libraries) seems to be: * Configure php with the chosen extensions as static * Add a static target to Makefile * Compile * Link library with embedder (a bit inefficiently by using the GUI) I think that could be done faster if instead you built all extensions as shared and modified the Makefile to convert all those dll to static libraries. Then you would build php once, and get the different stubs just by linking with different objects. You would need to change zend_API.h's ZEND_GET_MODULE to define a constructor function which autoloaded the module. That approach should work for most extensions. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
