[Ecls-list] SIMPLE-ERROR: In interpreted code, attempted to call a foreign function but ECL was build without support for that.

Juan Jose Garcia-Ripoll juanjose.garciaripoll at gmail.com
Sun May 19 20:47:51 UTC 2013

On Sun, May 19, 2013 at 12:40 PM, Dietrich Bollmann
<dietrich at formgames.org>wrote:

> In ecl/src/configure I found the option
>   --with-dffi             dynamic foreign function interface
>                           (system|included|auto|no, default=AUTO if libffi
>                           available)
> But I couldn't find anything similar in the windows ecl/msvc/Makefile.
> How do I compile the 64 bit version of ECL under Windows with dynamic
> foreign function support?

Currently ECL does not support this in the original sources because FFI has
evolved into a very complicated set of sources that cannot be built with
Microsoft's compilers: it demands mingw and other tools.

This may have changed recently, I do not follow libffi so closely, but, as
I said, the problem is not that ECL cannot be linked against libffi using
Visual Studio, it is just that I do not know how to do this integration
smoothly without further dependencies.

A more reasonable alternative that works on all ports (and is much faster)
would be to compile your code before loading it: it will just work even
without dffi. The FFI is only needed to create the wrappers, but once they
have been compiled they work regardless of the underlying implementation.


Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20130519/88cc6908/attachment.html>

More information about the ecl-devel mailing list