I don't know what that does. (I've never wanted to compile a separate module.) I'm not claiming the problem isn't solved already. :-)
It compiles a module in a separate directory. You don't need the main build-tree of the pike, just an installed pike.
How about a separate installation tree, like site-lisp (site-pike?), that doesn't get erased with installing new pike revisions?
Sounds like a good idea. Maybe not for C modules (which may require recompiling to be used with a new pike version), but for undumped pure pike modules (with appropriate #pike declarations).
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2003-01-26 19:43: Subject: Re: Bz2
I don't know what that does. (I've never wanted to compile a separate module.) I'm not claiming the problem isn't solved already. :-)
How about a separate installation tree, like site-lisp (site-pike?), that doesn't get erased with installing new pike revisions?
/ Mirar