From: Sam S. <sd...@gn...> - 2005-10-03 16:10:06
|
> * Tomas Zellerin <mryyreva@tznvy.pbz> [2005-10-03 15:06:34 +0200]: > >> >> if change in makemake.in >> if [ "${with_readline}" != ifpossible ]; then >> to >> if [ "${with_readline}" != yes ]; then >> >> clisp is build, but without readline. >> > > Originally, I was trying to make the readline interface work not as > module, but as a loaded file. I did not succeed in making it work on > Windows this way - e.g., readline function was succesfully defined, > but it did not work as expected. > > Are there some fundamental differences between using FFI as a module > and as a loaded file? a module is the way we bundle clisp add-ons for easy distribution. modules may use ffi (bindings/*, wildcard, matlab) or just plain C (syscalls, rawsock, pcre, berkeley-db). those that use ffi may use the traditional CLISP way (generate a C file and link it in), e.g., wildcard, or dlsym-based ffi (e.g., bindings/win32) the problem with dlsym-based ffi is that some systems lack dlsym, so if we make the readline module using dlsym it will not work on some platforms. -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://pmw.org.il/> <http://ffii.org/> <http://www.camera.org> <http://www.savegushkatif.org> <http://www.dhimmi.com/> If brute force does not work, you are not using enough. |