2008/9/7 Ken Raeburn <[EMAIL PROTECTED]>:
>
> Not if you want to build and install the full guile package and then link
> emacs against libguile, which is how I've generally done it. Or if you want
> to build both emacs and guile executables at once so you can test libguile
> without the rest of emacs. Of course, I could just drop a copy of guile
> into the source tree and tweak the build process to skip the 'guile' binary,
> or add wrapper functions that only link into that executable and cause the
> redirected calls to invoke malloc and friends after all.
OK, I see now.
> I could also create function-pointer variables that could be changed before
> guile initialization, and I may do it that way for my own use, but it's not
> clear to me that there'd be any value in feeding that back upstream.
Agreed, that's probably not worthwhile initially, until the
Emacs/Guile work advances to the point where others could try it out.
Neil
