libraries

Hello

I am using Common Lisp on Debian GNU/Linux and I have question about
libraries.

CLISP, CMUCL and SBCL share their libraries under
/usr/share/common-lisp/
and I can load them via asdf and the common-lisp controller.

GCL has its libraries under
ls /usr/lib/gcl-"version"
and the libraries are loaded by default.

How can I mix the systems? Especially I would like to use
cl-gd under GCL and the Tk binding under CLISP.

Thanks for your help.

Andreas Klein

.

Relevant Pages

  • Re: professional package use?
    ... Yet there are numerous open source Common Lisp ... Gives folks who maybe don't have the particular mentality ... > Not everything can, or ought, to be solved with libraries. ...
    (comp.lang.lisp)
  • Re: What are your favorite portable (or mostly portable) libraries
    ... I'm particulary interested in libraries that are ... > portable between many or all Common Lisp impls. ... cl-awk - Common Lisp package with the features of AWK and more. ... cl-sql-aodbc - CLSQL database backend, ...
    (comp.lang.lisp)
  • Re: Modernizing Common Lisp
    ... Since portability is just another variant of reusability, ... The good thing about Common Lisp and its ANSI standard is that it is ... Pick out _one_ Common Lisp implementation ... implementations, libraries, applications and services, or by buying ...
    (comp.lang.lisp)
  • A common library?
    ... Every now and then some guy proposes that "the Common Lisp Standard ... The main problem, of course, is that while libraries for such things ... For sockets, for example, there are trivial- ...
    (comp.lang.lisp)
  • Re: Interesting developments since "Beating the averages"?
    ... the differences between Common Lisp and Scheme, the conventional wisdom that they get here is that Scheme is a minimalist standard, in order to get anything practical done with it one needs a library that brings it up to the level of Common Lisp and, since in Common Lisp the library is standardized and in Scheme it's typically implementation specific, Common Lisp is in that respect superior. ... You don't need standards to get things done, you only need portable libraries. ... It seems that the only solution would then be to drop Common Lisp and go with a new Lisp dialect that doesn't suffer from the large number of implementations. ...
    (comp.lang.lisp)