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.

And if you have .cmod:s, you do need pike to build the module.

/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)

Previous text:

2004-01-26 20:25: Subject: Re: Pike @ Debian

---

On Mon, Jan 26, 2004 at 08:15:02PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum scribbled:

...

I don't think the build system needs to change. That it can't work if you put the files at place A but _tell the build system they are at place B_ isn't really a bug. There might be a point in allowing finer

If the build system was documented, then I wouldn't have to wait for somebody to stumble upon the problem. If you confirm what I asked about in the other posting and repeated below, then I'll fix it in no time.

...

granularity in the path specifications, so that certain files can be in one place and others in another, but that's not the problem here. Debian keeps all the files needed by the build system in one place, it just lies to said build system about what that place is.

If include_prefix is the only change that is _really_ needed, then it's trivial. OTOH, why does the build system have to be a build system at all? Why not just provide a simple pike.m4 file to be included in you module's aclocal.m4? It seems to me to be a bit overdone to have to install and launch the whole pike interpreter and the library in order to get a few strings for the compilation process - especially that you don't need pike to link your modules, all you need is the C headers.

marek

/ Brevbäraren