gmane.lisp.cello.devel

Re: Compiling

Kenneth Tilton — 2010-06-01T04:46:50


Kenneth Tilton wrote:

Hmmm, I see: (intern (conc$ "mk-" (symbol-name class)))

Not sure what's up there, but if that were

    (intern (conc$ 'mk- (symbol-name class)))

It would work in modern or ansi mode.

kt

Re: Compiling

Kenneth Tilton — 2010-06-01T03:10:07


Seth Burleigh wrote:

Aha. You have Modern mode Allegro CL? The trial edition? Any place you 
see me assembling a string and then interning it, look out! There will 
often be a string-upcase there, or some assumption about the case of 
symbol-name, or something like that.

I'll take a look at the macro.


Yep, this is how it goes, step by silly step, symbols, packages, ASDF 
sucks...


Anything current on Tk is good.

I actually figured out Cello was not really using cl-freetype any more 
when porting it to OS X recently (which came up short on one of the fonts).

kt

Re: Compiling

Seth Burleigh — 2010-06-01T02:38:33

K, fixed that. I'll retire for today,  but apparently the problem is
that you were defining a macro which ended up like this
(defmacro |mk-ARC| ...)
and when you try to normally use the macro, its looking for MK-ARC, not
mk-ARC.

Getting closer :) 


Are there any specific versions of the tk library that i have to use
(and also the freetype?)

Re: Compiling

Kenneth Tilton — 2010-06-01T01:56:21

They are defined by a macro, def-tk-something.

I guess you are building with ASDF?

Try a :force t on the whole thing. There may be a dependency missing 
that would make ASDF load as it goes.

ASDF really sucks.

kt

Seth Burleigh wrote:

Re: Compiling

Seth Burleigh — 2010-06-01T01:50:58

Where exactly is celtk:mk-arc and related defined?

Re: [cells-devel] Compiling

Frank Goenninger — 2010-05-30T13:56:28

Am 30.05.2010 um 01:59 schrieb Kenneth Tilton:


Yep. I had that going but did not complete that. Still, FTGLFromC works.


Seems as if gui-gemoetry and Celtk are still missing.


And it is still worth doing. I kept finding new things and beauties within Cello for more than two years of using it for various little apps.

Frank

Re: Compiling

Kenneth Tilton — 2010-05-29T23:59:55


Seth Burleigh wrote:

FTGL now has a C interface. I think the effort of converting to that is 
where I stopped to rethink the wisdon of resuscitating Cello and decided 
against.


My stuff compiles without warnings under the acl IDE, but asdf sucks so 
who knows? You'll find out at runtime.


Yeah, that's the kind of crud you have to slog through. Until Cello 
builds reaches ten I do not think things will get much better.

kt

Re: Compiling

Seth Burleigh — 2010-05-29T22:21:24

OK, so heres my notes on compiling. I haven't yet got the example
working, because of some missing functions. Any inputs on these missing
functions, where are they? Also, while reading the install-notes, i came
across this. Do i really need to do what it says? (ok , probably so, but
im hoping)

----------- BIG PROBLEM
--------------------------------------------------------
Libraries. For win32, the PC4 release includes the DLLs I use (well,
except those you should find in /windows/system32). Linux/Mac OS X
really have their work cut out for them. Building Freeglut and
ImageMagick (and FreeType) may just work for you as typical Linux
installs, but FTGL as I have done it requires to build with the included
FTGLFromC.cpp and a modified FTGLExtrdFont.h built into the
library .SO. 
-----------------------
FUNCTIONS MISSING!!!:
compiling cello:

; compilation unit finished
;   Undefined functions:
;     CELLO::KEYSYM-SYM CELTK:MK-ARC CELTK:MK-BITMAP CELTK:MK-CANVAS
CELTK:MK-CHECKBUTTON CELTK:MK-ENTRY CELTK:MK-FRA

Re: Compiling

Frank Goenninger — 2010-05-29T15:15:47

Am 29.05.2010 um 06:57 schrieb Seth Burleigh:


It has all this... I've not used Cello for more than a year - but I had it working on OS X and Linux (debian). I was about 50% down the road of a major re-write of the inner workings of Cello (as it was actually too much effort to understand - and keep understanding - of the Cello code for me ;-). Due to work-for-money reasons I never got to finish this, unfortunately. I aimed at eliminating some of the glue code for FTGL and other optimizations.

I still do use Cells, of course - heavily, so.

Cheers
  Frank

Re: Compiling

Kenneth Tilton — 2010-05-29T15:24:48


Seth Burleigh wrote:

OK, good. I should have offered that our experience has been that in the 
end Cello can be gotten running after running down not too many Lisp 
implementation differences and the like. And it has been to Linux and OS 
X at various times, so some of the diffs have been sorted out. ie, There 
are no interesting show-stoppers out there.

I ran out of steam on moving Cello to github, so c-l.net was the right 
place.

kt

Re: Compiling

Seth Burleigh — 2010-05-29T15:13:49

Well, i got alot built, i'll let you know if i become stuck, right now
im looking at a bug in asdf itself. I'll also make sure to describe all
the steps once i get everything successfully compiled.

Re: Compiling

Seth Burleigh — 2010-05-29T13:42:46

I guess the first step is to see if i got the right version! I got cello
from

http://common-lisp.net/cgi-bin/viewcvs.cgi/?root=cello

and i retrieved cells and utils-kt from your github site. Im using sbcl
1.0.38 under linux (ubuntu 10.04).

Re: Compiling

Kenneth Tilton — 2010-05-29T05:48:58


Seth Burleigh wrote:

Well I will be happy to help you get Cello going, because OpenGL is 
certainly fast and also expressive enough for graphing, and I have had 
no problem rolling arbitrary widgets from simple building blocks.

Did you find Cello on GitHub or common-lisp.net? What are your 
development and delivery OSes?

kt

Re: Compiling

Seth Burleigh — 2010-05-29T04:57:33

Oh, ok. I was looking at that new project of yours, looks interesting,
but I decided I needed something that was quite a bit quicker than a web
app (fast, real time graphing and the  easy customizable widgets that i
have heard cello is capable of is also a must).

Re: Compiling

Kenneth Tilton — 2010-05-29T02:02:07


Seth Burleigh wrote:

We've had some patches in re the mop package name and other stuff to 
make it more portable. One user did a major cleanup of Cello but never 
got to the point where it would be released. And I am moving to the web 
with a new project based on qooxdoo. Doubt I'll ever get back to Cello.

ie, it is very close to being a dead project. Oh, and I only know of one 
person for sure who got it all working.

kt

Compiling

Seth Burleigh — 2010-05-28T23:58:00

Ive got the code for cello. Im attempting to get cl-opengl working.

Ive hade some problems. First, 

(1) When loading libgl.so and libglu.so , it has some weird directory
under which it expects libgl and libglu to be under, on unix. I cant
imagine why this is in there since in linux operating systems the
libraries are installed in a standard location. I replaced it with
cffi:load-foreign-library "libGL.so",etc.

(2) Now, I get

Execution of a form compiled with errors.
Form:
  (DEFUN-FFX INT
    glut
    glutCreateWindow
    (CSTRING TITLE))
Compile-time error:
  (during macroexpansion of (DEFUN-FFX :INT
    ...))
Don't know how to cast CSTRING
   [Condition of type SB-INT:COMPILED-PROGRAM-ERROR]


Anyone know how to fix this, im on sbcl 1.0.38 on ubuntu.

So, question is what is the state of this code? Some of it, like cells
and its dependencies, has a bias towards allegro. For example, it
depends on the mop package which is easily fixed by requiring closer-mop
and adding mop as a nickname. Not exactly an