Hi,
This is sort of a final plea to the Clisp user community. If anyone of you guys is
able to make Clisp on Win32 call a C function, I would die to know how you do it.
I can't quite grok what "Foreign Function Interface" really means, so step by
step hints are appreciated[1].
I have mistakingly commited myself to a language I don't know very well -- Lisp.
I was a happy user initially, having breezed through development (interactive
development with emacs' C-M-x and clisp is great.) but only now did I realize that
most of the tools mentioned in the cliki do not work with Clisp, and even most of
those which do, do not work with Clisp on Win32.
I still have a few days left to turn in my work (SWE assignment for school.) so I
will go ahead and rewrite my app in TCL (I was already using lisp2wish as a GUI.)
Meanwhile, I would like to grasp FFI cold, so I never feel this weak and helpless
again.
--
[1] I understand that clisp's FFI somehow means "static linking", IOW, compile
Clisp sources and link against your intended library. But Clisp requires Unix
to compile for Win32. Is that how you went about it?
Andy Reiter wrote:
> I still have a few days left to turn in my work (SWE
> assignment for school.) so I will go ahead and rewrite my
> app in TCL
You may want to take a look at Python too.
--
J.... B....
-----------== Posted via Newsfeed.Com - Uncensored Usenet News ==----------
http://www.newsfeed.com The #1 Newsgroup Service in the World!
-----= Over 100,000 Newsgroups - Unlimited Fast Downloads - 19 Servers =-----
> * In message <····························@posting.google.com>
> * On the subject of "FFI Concept, way over my head."
> * Sent on 20 Oct 2002 21:57:05 -0700
> * Honorable ·······@flop.co.uk (Andy Reiter) writes:
>
> This is sort of a final plea to the Clisp user community.
final? hmm - I have not seen a single message from you on <clisp-list>.
> If anyone of you guys is able to make Clisp on Win32 call a C
> function, I would die to know how you do it. I can't quite grok what
> "Foreign Function Interface" really means, so step by step hints are
> appreciated[1].
look through the <clisp-list> archives for messages from Joerg Hoehle.
Ask <clisp-list> and our win32 experts will answer your specific questions.
OTOH, if you compile CLISP with cygwin, all modules should work just
like on any Unix box.
> But Clisp requires Unix to compile for Win32.
Huh?!!!
--
Sam Steingold (http://www.podval.org/~sds) running RedHat8 GNU/Linux
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html>
186,000 Miles per Second. It's not just a good idea. IT'S THE LAW.
Sam Steingold <···@gnu.org> wrote in message news:<··············@loiso.podval.org>...
> > This is sort of a final plea to the Clisp user community.
>
> final? hmm - I have not seen a single message from you on <clisp-list>.
Fair enough, but I have searched the mailing list before I posted
this, and got
only question and very little answers. They were mostly threads about
interfacing with SDL and OpenGL. The other thing is, Clisp is a moving
target
and I have seen threads you had about improving FFI, so I thought
things might
have changed.
> > If anyone of you guys is able to make Clisp on Win32 call a C
> > function, I would die to know how you do it. I can't quite grok what
> > "Foreign Function Interface" really means, so step by step hints are
> > appreciated[1].
>
> look through the <clisp-list> archives for messages from Joerg Hoehle.
> Ask <clisp-list> and our win32 experts will answer your specific questions.
Will do. The only reason I am asking the question is so I can take
part in the
development and write bindings for important libraries.
> OTOH, if you compile CLISP with cygwin, all modules should work just
> like on any Unix box.
>
> > But Clisp requires Unix to compile for Win32.
>
> Huh?!!!
Ummmm, I have Clisp 2.30 and in the file $SOURCES/win32msvc/Install,
it shows
the procedure for compiling and installing Clisp and it gives explicit
instructions on how use a Unix NFS partition for compilation.
I am not making this up. Thanks though, I will try cygwin.
> * In message <····························@posting.google.com>
> * On the subject of "Re: FFI Concept, way over my head."
> * Sent on 22 Oct 2002 20:58:39 -0700
> * Honorable ·······@flop.co.uk (Andy Reiter) writes:
>
> The only reason I am asking the question is so I can take part in the
> development and write bindings for important libraries.
In that case you might want to work off the CVS and read <clisp-devel>.
> > > But Clisp requires Unix to compile for Win32.
> >
> > Huh?!!!
>
> Ummmm, I have Clisp 2.30 and in the file $SOURCES/win32msvc/Install,
> it shows the procedure for compiling and installing Clisp and it gives
> explicit instructions on how use a Unix NFS partition for compilation.
Yuk. This is so obsolete...
I will fix the INSTALL file. Thanks.
--
Sam Steingold (http://www.podval.org/~sds) running RedHat8 GNU/Linux
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html>
MS Windows vs IBM OS/2: Why marketing matters more than technology...