Hi Sam,
OK -- I resolved it. After building the modules, I want to auto-load the file in clisp.
Using the guidance from:
http://www.lispforum.com/viewtopic.php?f=15&t=1445
I created a ~/.clisprc.lisp file and put the following command there:
(load "/usr/local/Cellar/clisp/2.49/lib/clisp-2.49/pcre/pcre.lisp")
And it worked.
Here are the modules loaded in:
(:SWANK :PCRE :REGEXP :SYSCALLS :I18N :LOOP :COMPILER :CLOS :MOP :CLISP :ANSI-CL :COMMON-LISP :LISP=CL :INTERPRETER :SOCKETS :GENERIC-STREAMS :LOGICAL-PATHNAMES :SCREEN :UNICODE
:BASE-CHAR=CHARACTER :WORD-SIZE=64 :UNIX :MACOS)
Thanks,
-Sam
On Oct 7, 2012, at 12:29 PM, Sam Krishna <sam.krishna@...> wrote:
> Hi Sam,
>
> OK, I think I've got pcre built as a clisp module now. Here's my directory listing for the main clisp path:
>
> base/
> build-aux/
> data/
> dynmod/
> linkkit/
> pcre/
>
> In the pcre/ directory, here are the files there:
>
> pcre/Makefile
> pcre/cpcre.o
> pcre/link.sh*
> pcre/pcre.fas
> pcre/pcre.lisp
> pcre/preload.lisp
>
>
> In my .emacs file, here's how I have Slime configured:
>
> (setq inferior-lisp-program "/usr/local/bin/clisp -K base") ; your Lisp system
> (add-to-list 'load-path "~/Projects/Lisp/slime/") ; your SLIME directory
> (require 'slime)
> (setq slime-net-coding-system 'utf-8-unix)
> (slime-setup '(slime-fancy))
>
> Currently, my *FEATURES* show the following loaded modules whenever I launch Slime:
>
> (:SWANK :REGEXP :SYSCALLS :I18N :LOOP :COMPILER :CLOS :MOP :CLISP :ANSI-CL :COMMON-LISP :LISP=CL :INTERPRETER :SOCKETS :GENERIC-STREAMS :LOGICAL-PATHNAMES :SCREEN :UNICODE
> :BASE-CHAR=CHARACTER :WORD-SIZE=64 :UNIX :MACOS)
>
> NOW, how do I get pcre/pcre.lisp to automatically load when I launch Slime/clisp from within Emacs? (This is when I type M-x slime [Enter]). This way I'll see :PCRE appear as well.
>
> Thanks,
>
> -Sam
>
>
> On Oct 7, 2012, at 9:19 AM, Sam Steingold <sds@...> wrote:
>
>>> * Sam Krishna <fnz.xevfuan@...> [2012-10-06 18:39:18 -0600]:
>>>
>>> Platform: Mac OS X (Mountain Lion) 10.8.2
>>> clisp v. 2.49
>>
>> did you install clisp yourself?
>> if yes, just pass "--with-module=pcre" to the top-level configure or add
>> pcre to the MODULES Makefile variable.
>> if no, then your clisp vendor should have a clisp-pcre package as per
>> "Additional Information for Maintainers of Binary Packages" in clisp/unix/INSTALL.
>>
>>> Doesn't seem to make any sense to me b/c *MY* confusion around FFI.
>>
>> clisp pcre module does not use ffi
>>
>>> Can anyone point me in the right direction? I'm not clear if I *NEED*
>>> to create a module, or already link it, or what?
>>
>> you need to download the module and build it using your current clisp
>> installation.
>>
>> --
>> Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000
>> http://www.childpsy.net/ http://thereligionofpeace.com http://ffii.org
>> http://think-israel.org http://pmw.org.il http://camera.org
>> Genius is immortal, but morons live longer.
>
|