[Ecls-list] SIMPLE-ERROR: In interpreted code, attempted to call a foreign function but ECL was build without support for that.
dietrich at formgames.org
Mon May 20 02:15:20 UTC 2013
> 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
I tried to do so - but for some reason I never get it work...
A very simple HOWTO explaining step by step how to compile and load a
simple example file ( for instance the sin / cos example in
examples/ffi/cffi.lsp ) would be most helpful!
I tried all kind of permutations of (compile-file ...) with different
parameters, together and without (require :cmp), etc. but I seem to be
unable to make sense out of the documentation and error messages and always
fail to get a working example...
I am currently trying to understand the msvc build files of ECL - but would
be very grateful about a faster solution...
Anyway, thank you very much for your fast and detailed answer! Your
one-man support is quite impressive - actually much more than the
"professional" (and commercial) support of most companies!
On Mon, May 20, 2013 at 5:47 AM, Juan Jose Garcia-Ripoll <
juanjose.garciaripoll at gmail.com> wrote:
> 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
>> 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...
More information about the ecl-devel