Update of /project/cells-gtk/cvsroot In directory common-lisp:/tmp/cvs-serv9159
Modified Files: INSTALL.TXT Log Message: New procedure *gtk-lib-path* is gone! Note testing of SBCL and new windows GTK+ lib
--- /project/cells-gtk/cvsroot/INSTALL.TXT 2006/01/03 19:13:50 1.1 +++ /project/cells-gtk/cvsroot/INSTALL.TXT 2006/02/16 18:09:31 1.2 @@ -7,16 +7,13 @@
STEP 1: EVERYONE: Start lisp, change to this directory and do (load "load")
-STEP 2: EVERYONE: If STEP 1 didn't go well, look at the settings of - *gtk-lib-path* in file ./root/gtk-ffi/gtk-ffi.asd +STEP 2: EVERYONE: (test-gtk::gtk-demo)
-STEP 3: EVERYONE: (test-gtk::gtk-demo) - -STEP 4: ANYONE (optional) make libcellsgtk, (or get it from the cells-gtk site). To make: - 4a) In ./root/gtk-ffi 'make' - 4b) Move the library created to whatever *gtk-lib-path* is set to. - 4c) Uncomment the line (pushnew :libcellsgtk *features*) in ./root/gtk-ffi/gtk-ffi.asd - 4d) Recompile the distribution (remove fasls and type (load "load") again. +STEP 3: ANYONE (optional) make libcellsgtk, (or get it from the cells-gtk site). To make: + 3a) In ./root/gtk-ffi 'make' + 3b) Move the library created to where it will be found (Linux see /etc/ld.so.conf). + 3c) Uncomment the line (pushnew :libcellsgtk *features*) in ./root/gtk-ffi/gtk-ffi.asd + 3d) Recompile the distribution (remove fasls and type (load "load") again.
TESTED ON: @@ -28,18 +25,17 @@ Lispworks 4.4 Pro, CMUCL 19c, CLISP 2.36 + SBCL 0.9.9.1
NOT TESTED SINCE SWITCHING TO CFFI: (as of 2006-01-03): AllegroCL - MACOS - SBCL - never tested, but probably pretty close to OK. + MACOSX
;;; -------- Windows Users ---------------
- Get GTK and Install
- http://gimp-win.sourceforge.net/stable.html + http://gimp-win.sourceforge.net/stable.html (I used version 2.8.9)
Executing the setup.exe should add "C:\Program Files\Common Files\GTK\2.0\bin" to your path. You can verify that it has: @@ -50,6 +46,8 @@
Note: On windows under emacs with slime, the gtk window does not popup. You must start the application from a dos prompt. + (Solutions to this problem welcome!, probably involves putting something + like a call to gtk-iteration-do into some slime loop through a hook.)
Known bugs: On Windows: Clisp crashes if