How can it save space? You really _do_ need pike to compile pikemodules. Anything else is highly volatile, it's _extremely_ tough (although theoreticall possible) to dump .pmod files to .pmod.o without pike, but I would not attempt it (a pike module is always a .so and a .pmod nowdays, and the .pmod needs to be dumped).
/ Per Hedbor ()
Previous text:
2004-01-26 20:47: Subject: Re: Pike @ Debian
On Mon, Jan 26, 2004 at 08:35:02PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum scribbled:
The main reason is that you can have several pikes installed or semi-installed. The -x module systems lets you start up any pike of your choice with any additional flags you might need, and get the module compiled for that exact environment.
PIKE_MACRO(7.4.123)
would do the trick just fine. You can pass the version on the configure command line
And if you have .cmod:s, you do need pike to build the module.
Sure, but they are not needed to build e.g. Caudium or PHP4 modules - and in Debian it saves over 40MB in dload size for the autobuilders. Not something to be ignored.
marek
/ Brevbäraren
pike-devel@lists.lysator.liu.se