I'm not sure who made changes to precompile.pike, so I don't want to make this change myself on the chance there's a reason for it.
I installed the 7.8 beta a few days ago and the include/pike/precompile.pike installed still doesn't compile, as it uses a relative path to the real Tools.Standalone.precompile that's only valid inside the source tree. It would seem that you can't use the same file for both purposes while still using a relative path. Any reason why the relative path couldn't be changed to "inherit Tools.Standalone.precompile"? As it stands now, most external cmod modules are broken because of it.
Bill
I think the reason for the relative path is that you want to use the current precompiler even if you precompile using an older pike. In an installed pike, that is probably moot. But it might be bad to change it in the source tree.
You mean something like
#ifdef NOT_INSTALLED #include "....."; #else inherit X.Y; #endif
? Yes, I imagine so.
Although probably not _exactly_, since precompile.sh doesn't define -DNOT_INSTALLED unless it's using the pike inside the build tree. So some other define would probably be appropriate.
Is is possible that the appropriate define doesn't exist? It doesn't seem like a differentiation is made between the currently being built pike and the installed one.
pike-devel@lists.lysator.liu.se
-
Bill Welliver -
hww3 ＠ Pike developers forum -
Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum
-
Martin Stjernholm, Roxen IS ＠ Pike developers forum