Please add cl-tcod #368

trollusk opened this Issue Sep 18, 2012 · 7 comments


None yet

3 participants


Common Lisp wrapper for the Doryen Library (, a "free, fast, portable and uncomplicated API for roguelike developers providing an advanced true color console, input, and lots of other utilities frequently used in roguelike games."

Mercurial repository at:


I could not get that C library built on my Debian system. Is there any easy way to install it?

trollusk commented Nov 4, 2012

Prebuild binaries are available for download at:

Just put libtcod*.so somewhere in your library path. It also needs libSDL to be installed.


Anything else I can do to progress this?

Okasu commented Jan 19, 2013

@quicklisp, builds just fine, add it please.

@eeeickythump, can you update your readme, since there is no hello-world in your tcod package:

localhost: sbcl
This is SBCL 1.1.3, an implementation of ANSI Common Lisp.
More information about SBCL is available at <>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
* (ql:quickload :tcod)
To load "tcod":
  Load 1 ASDF system:
; Loading "tcod"
* (tcod:hello-world)

debugger invoked on a SB-INT:SIMPLE-READER-PACKAGE-ERROR in thread
#<THREAD "main thread" RUNNING {10029E8EC3}>:
  The symbol "HELLO-WORLD" is not external in the TCOD package.


Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [CONTINUE] Use symbol anyway.
  1: [ABORT   ] Exit debugger, returning to top level.


I couldn't get the prebuilt binaries working. Can you throw it into a deb or something?

trollusk commented Mar 5, 2013

@Okasu - I have made the changes (hello-world exists but was not exported from the tcod package).
@quicklisp - I have no problems with the precompiled libraries on Mac, Linux or Windows. Others don't seem to have problems either. Loading external libraries is often fiddly and IMHO it seems strange (not to mention labour-intensive for you) to use whether a binary library loads on one computer (yours), rather than whether the lisp code compiles and loads, as the barrier to quicklisp distribution. I think if the lisp compiles and loads then that should be good enough. Trying to test every wrapper library by installing its .dll/.so/etc files must be a thankless task.

PS one problem some people have is that the font image file 'terminal.png', which is distributed with the library, has to be in the path when the library is loaded.


The lisp code does not compile and load, though.

I'm willing to keep plugging away at it, but I don't have a lot of time and having a deb would make it much, much easier for me to try.

@quicklisp quicklisp closed this Jul 25, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment