February 2004 - cells-devel - mailman3.common-lisp.net

[cells-devel] Cello moving out
by Kenny Tilton 26 Feb '04

26 Feb '04

Cello is growing up (ported to Linux by Frank Goenninger) and is moving out to a place of its own: http://common-lisp.net/mailman/listinfo/cello-devel http://common-lisp.net/mailman/listinfo/cello-announce http://common-lisp.net/mailman/listinfo/cello-cvs Things should be quiet here until a planned massive re-write of Cells, which may not happen for a while, but if I run into a problem that traces back to the weakness I see in state propagation, look out. :) Sorry for all the spam. kenny -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application

1 0

[cells-devel] Re: cells test breakloop
by Kenny Tilton 25 Feb '04

25 Feb '04

mikel evins wrote: > Kenny, > > When running cells::cv-test I hit a breakloop; the cells docs say that > this means something's wrong. > > Just for a sanity check (and because I'm considering whether to use > cells for some knowledge modeling in a personal project) I tried > running the tests from Lispworks, and broke in exactly the same way. > The output below is copied from OpenMCL 0.14.1, but is exactly the > same (modulo object numbers and break prompts) as that from Lispworks: Ah, that's one I had fixed for a while and then for some reason decided to break again. I am fixing it over here, but you can just either: 1. move on to try lesson-14 or starter; or 2. In c-break and c-calculate-and-set, change BREAK to ERROR Lispworks is right, ACL is wrong: break should land you in the debugger regardless of any errors. What I am doing in a few places during CV-TEST is deliberately coding usage errors with Cells to confirm user errors are signalled, but then I want the test to run to completion, so I trap the errors and actually signal a "test-failed" error if no error gets trapped. Under ACL the /real/ Cell error gets signalled with break and the test can trap it, but that is wrong. kenny

1 0

Re: Report on Celloglut and ACL 5.0.1 [was [cells-devel] Emailing: celloglut.zip
by Raistlin Magere 25 Feb '04

25 Feb '04

>>Loading Cloucell.lpr insteads gives a few errors still (not many at all): >> >>*Error Part1* >>; While compiling CELLS-TIME-REPORT in c:\dvx\cells\debug.lisp: >>Warning: EXCL::TIME-REPORT should be given exactly 9 arguments. It was >>given 8 arguments. >>Problem detected when processing >> (EXCL::TIME-REPORT CPU-GC-USER CPU-GC-SYS ...) >>inside (BLOCK CELLS-TIME-REPORT (TRC "cpu-gc-user" CPU-GC-USER) ...) >>inside (PROGN (BLOCK CELLS-TIME-REPORT (TRC "cpu-gc-user" CPU-GC-USER) >>...)) >> >> >>*Error Part2* >>in "structure-view" >>Error: No class named: EXCL::STRUCTURE-EFFECTIVE-SLOT-DEFINITION. >>[condition type: PROGRAM-ERROR] > >Sorry, I forgot about those. I'll nail those now. > >> >> >>*Error Part3* >>Cannot find c:\dvx\cello\lesson6.lisp. Will skip and continue compiling >>project. > >I am getting confused now, but I think the project to try is just plain >cello.lpr. new reorg underway (and last night's distro is definitely for >use with cello.lpr--you'll still have the above errors, but they can be >swept under the carpet). > Ok running cello.lpr (after having deletead all the fasl files) gives me only *Error Part1* i.e. the time-report error. Again lesson-14 loads fine just after loading. Is there any set of other tests (like lesson-14) that I can run (i.e. without having to read your code to figure out how to write my own tests - which I'll probably do at some other time)? raistlin _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail

1 0

Report on Celloglut and ACL 5.0.1 [was [cells-devel] Emailing: celloglut.zip]
by Raistlin Magere 25 Feb '04

25 Feb '04

Ok: Opengl-ffi.lpr loads fine and running lesson-14 shows the window with the fonts and moving text fine. Loading Cloucell.lpr insteads gives a few errors still (not many at all): *Error Part1* ; While compiling CELLS-TIME-REPORT in c:\dvx\cells\debug.lisp: Warning: EXCL::TIME-REPORT should be given exactly 9 arguments. It was given 8 arguments. Problem detected when processing (EXCL::TIME-REPORT CPU-GC-USER CPU-GC-SYS ...) inside (BLOCK CELLS-TIME-REPORT (TRC "cpu-gc-user" CPU-GC-USER) ...) inside (PROGN (BLOCK CELLS-TIME-REPORT (TRC "cpu-gc-user" CPU-GC-USER) ...)) *Error Part2* in "structure-view" Error: No class named: EXCL::STRUCTURE-EFFECTIVE-SLOT-DEFINITION. [condition type: PROGRAM-ERROR] *Error Part3* Cannot find c:\dvx\cello\lesson6.lisp. Will skip and continue compiling project. and that's it. Ah by the way in cloucell.lpr you still refer to "c:\\dev\\cello\\*whatever*" rather than "c:\\dvx\\cello\\*whatever*". _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail

2 1

[cells-devel] whoa, porters!!
by Kenny Tilton 25 Feb '04

25 Feb '04

Just killed about six hours on this: app ran fine when I built using the ACL project manager. Then I built with ASDF just to confirm the ASD files were complete. Suddenly the demo (the lighting panel) looked black and white, tho yellow check marks still appeared yellow. Quite a few hours into the show I discover the light positioner, if clicked, starts to bring things back to normal. But it starts as if it were uninitialized. Also, a few more clicks like this and we lose the whole IDE. Finally at hour six one of the monkeys accidentally changes the: (declaim (optimize...) at the top of the asd files to match the project manager defaults, and we are back in business. Under ACL/win32, that is, with less-than-optimal optimize settings. Which tells me... I got serious FFI declaration issues. I have been aware for some time that ACL can be very forgiving in this regard, and now I am guessing that goes away as the speed optimization gets cranked. So the good news is that I just need to crank the settings and then I should be able to debug my ffi work within ACL, my strongest environment. The upshot for porters is that their compilers may not be as helpful as ACL's, even with the safest and slowest settings. In fact, maybe I should test under Lispworks. That consistently broke on things ACL could handle, but it always turned out ACL had been letting me get away with murder. Well, ACL /is/ my strongest platform, and I have found a way it seems to make it less forgiving, so I may as well stay here until it all works with the toughest of settings, then see if LW is any less forgiving. There is no harm in trying if you manage to get a clean build and shared libs loaded and callbacks from C into Lisp working, but if the lighting panel comes up black and white (no apparent shading) and no spinning object (teapot)--bingo. btw, that apparent b&W is just bogus values for the ambience for the light. ambience is even lighting across a scene, so wicked bright ambience brings everything into high contrast. I will shortly put up CelloGlut.zip with this issue unresolved. The optimizations in the source /have/ been eased to make AllegroCL work when built via ASDF, but what your compiler does with what I am guessing is bad FFI work may still break things. kt -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application

2 2

[cells-devel] cells-devel delivery disruption
by Kenny Tilton 25 Feb '04

25 Feb '04

sorry, everyone. cells-devel started (occasionally) demanding moderator approval, and I had forgotten any and all passwords. erik at cl.net bailed me out this am, and we should be ok until i get stupid again. :) kenny -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application

1 0

[cells-devel] Emailing: celloglut.zip
by Kenny Tilton 25 Feb '04

25 Feb '04

Hopefully this gets thru. Too whipped to fire up the NT box where Yahoo's Java client for maintaining the web site works. I have mail into cl.net requesting my passwords be reset so I can start using the FTP there. cheers, kt -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application

1 0

[cells-devel] God Bless Lispworks Again
by Kenny Tilton 25 Feb '04

25 Feb '04

Wow, I must have had to fix six things, but now the awesome lighting panel runs identically under ACL and LW on win32. And a problem I had even under ACL with nested windows is gone. Life is good. :) Stepping out for a well-earned pint, but I plan to upload before retiring so Europe has the best possible code to work from. kenny -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application

1 0

[cells-devel] God bless Lispworks
by Kenny Tilton 25 Feb '04

25 Feb '04

Lispworks wasted no time going straight upside my head over an oddity caused by Freeglut history, I think: fonts are identified by enums 0, 1, 2 etc, but the parameter is declared in C as a pointer to a font! God bless static typing. AllegroCL I guess does things helpfully in this regard if speed/safety are set right, if not it does things insanely/silently. Lispworks just slapped me. The upsetting thing is that a couple of hours ago I happened to notice that some calls to the glut font functions had the ID wrapped in (make-ff-pointer...) and others did not. I know I was tired at that point because one of my cardinal rules is to fix anything like that whether or not I think it is related. Now Lispworks is yelling about something else. I do not think it should be, but I have to give LW the benefit of the doubt. kt -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application

1 1

[cells-devel] Re: more portabello notes
by Kenny Tilton 25 Feb '04

25 Feb '04

Mikel, Hope you don't mind me replying on cells-devel. One never knows who might have something to contribute, and it might be good for team spirit knowing others are banging on this. I know it does my spirits good, esp. after a day like this (which suddenly just got a lot better--more separately). mikel evins wrote: > Just a brief status; I spent some time on it today. I'm hung on > getting the UFFI stuff to behave properly with OpenMCL 0.14.1, but > only because I have to do some other stuff. > > More progress soon. I am hopeful, because I hear MCL as a rule is strong on FFI, and methinks UFFI has long supported it. Thx for your efforts. kenny -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application

1 0

[cells-devel] PortaCello 1.0: MagickFlipImage and others not available on Linux...
by Frank Goenninger 25 Feb '04

25 Feb '04

Hi all: Hmmmmm - this is a strange one again: I cannot find a source for ImageMagick (the library) where the functions MagickFlipImage, MagickGetImageWidth, and MagickGetImageHeight (and possibly more) functions are implemented. In the sources I have of ImageMagick (version 5.5.7) there are no such functions. I am using the C shared library of ImageMagick. There is also a C++ shared lib... Anyone using that? Kenny, which version do you use? And I thought I'd see something on the screen after solving the shared lib loading problem... ;-)) Thx for feedback. Regards, Frank

2 2

[cells-devel] [Fwd: Re: [spr28621] AllegroCL6.2 Trial user attempt to load his C++ shared library fails]
by Frank Goenninger 24 Feb '04

24 Feb '04

Solved! Great support from Franz! Simple cause - simple fix in the current state of Cello. But with ugly consequences for a production environment. Summary: ACL identifies foreign files by their endings. A ".so" file is recognized as a shared library - but most shared libs on Linux have a version info behind the ".so". Example: "libc.so.6" ... As these are different from file to file the recognition fails. Unfortunately it is not helpful to make a symbolic link that is named just "libc.so" (to stay with the above example). See below for details. Regards, Frank -----Forwarded Message----- From: Lois Wolf <lwolf(a)franz.com> To: frank_goenninger(a)t-online.de Cc: support(a)franz.com, frank_goenninger(a)goenninger.com, sales(a)franz.com Subject: Re: [spr28621] AllegroCL6.2 Trial user attempt to load his C++ shared library fails Date: Tue, 24 Feb 2004 13:37:44 -0800 Frank Goenninger: In Allegro CL 6.2 only files for which the file extension is an element of the list which is the value of the unexported symbol excl::*load-foreign-types* are recognized as foreign files. (This behavior is likely to be improved in Allegro CL 7.0) To make your file libftglint.so.1 recognizable to Allegro CL 6.2 as a foreign file, you can push "1" onto the value of excl::*load-foreign-types*, change the name of the file, or create a symbolic link with extension .so and load that. Please send any further email related to this problem report to support(a)franz.com with the identifier spr28621 in the subject line. Thanks, Lois Wolf Franz Inc., http://www.franz.com/ lwolf(a)franz.com 555 12th St, Suite 1450 (510) 452-2000; Fax: (510) 452-0182 Oakland, CA 94607

1 0

[cells-devel] Re: Problem Report: frgo/001/a0100: Cannot load C++ shared library
by Frank Goenninger 24 Feb '04

24 Feb '04

Dear Support Team: Here is some additional info about observations I made when trying to fix the problem outlined below: 1. In some cases ACL fails to load shared libs when the path points to a symbolic link instead of a real file. 2. The error is related to the file identification behavior of `load': * In case of correctly identifying the file as a foreign file the message appearing is "; foreign loading ..." * In case of not correctly identifying the file as a foreign file the message is (consistently) "; loading ..." So I wanted to direct this into finding out how `load' identifies foreign files as such. Unfortunately, I wasn't able to find a lower level call that "really loads a foreign file" (assuming load is just the top layer and the interface to underlying machinery). Any hints are appreciated. Thanks again. Best regards, Frank Goenninger On Tue, 2004-02-24 at 00:01, Frank Goenninger wrote: > Dear Support Team @ Franz: > > I am currently struggling to load a shared library using `load'. > > I would appreciate your help in sorting this out. Thank you very much > in advance! > > I. DRIBBLE FILE > > See attached dribble-bug file for a session transcript and system infos. > > II. PROBLEM DESCRIPTION > > Product: ACL 6.2 Trial > Plattform: Debian/Linux, Kernel 2.4.20, glibc3.3 > > I have a "homebrew" shared library that contains several C++ object > files. When I try to load that shared library I consistently get the > following error: > > ; Loading /home/frgo/projects/cello/ftgl-int/libftglint.so.1 > Error: Attempt to take the value of the unbound variable > ^?ELF^A^A^A^A^A^A .... > [condition type: UNBOUND-VARIABLE] > > A first interpretation on my side was that the generated shared > library is somehow damaged in the format and `load' is unable to > determine the right way to actually load it. So I wrote a short > C program to test if I can load it using plain C methods. > > This succeeds - the functions used are dlopen, dlsym, and dlclose. > > See section III. Example/Test of this email for the actual source > code. > > A second interpretation would be that the C++ shared library loads > into different memory regions than a normal C shared library - > thereby destroying memory regions occupied by the AllegroCL image. > But this is beyond my testing possibilities... > > I checked carefully all documentation for AllegroCL 6.2 on your > web site and also did some googling for relevant info - no luck... > > III. Example/Test Source Code > > Attachment "Makefile": a generated Makefile, to be called by `make'. > Attachments "FTGLFromC.cpp", "main.cpp": source code files. > Attachment "libftglint.so.1": The shared lib built from FTGLFromC.cpp > and a futher, precompiled static library. > Attachment "ftgl.lisp": The Lisp source file containing the code to > load the shared libs. > > Note: Loading plain C shared libs works as expected. > > The Lisp source uses UFFI as a layer in between AllegroCL's own > foreign function interface. For AllegroCL the call to > uffi:load-foreign-library simply translates into a call to > load. > > Of course I am ready to answer questions. You may reach me by phone: > > +49 7123 932355 > > or by email. Just reply to this email. > > THANKS AGAIN! > > Best regards, > > Frank Gönninger > > -- > Frank Gönninger, DG1SBG > Bempflingen, Germany > >

1 0

[cells-devel] loading under Linux
by Kenny Tilton 24 Feb '04

24 Feb '04

In case you missed it on cll today: Kenny Tilton <ktilton(a)nyc.rr.com> writes: >>>>>>I am doing the latter because one porter is having trouble so far >>>>>>loading on Linux the FTGL lib I use for fonts under win32. And anyway, >>>>>>it would be nice to have these libraries as clearly delineated >>>>>>components one can use or not without giving up the rest of Cello. >> >>>> what's his problem? FTGL works here (gentoo GNU/Linux, not sure if i >>>> haven't compiled it myself though). > >> >> Are you using FTGL from Lisp? Without C glue? nope. i misunderstood "loading on Linux the FTGL lib". sorry. >> What I did on win32 was write a few lines of C glue to get at the C++ >> FTGL classes, then rebuild the FTGL dll with that code. I believe the >> porter created a .SO for the C glue, linking that with a virgin FTGL >> static lib. AllegroCL on Linux then screams about something being >> unreadable when he tries to load the glue SO. Look for a recent query >> here from Frank G. He is able to load SOs as a rule, but the ones he >> builds have an issue, so it is probably some obscure linker >> incantation or compiler directive that is needed. Ideas welcome. i'm doing something similar but with cmucl, i wanna use my favorite media library from lisp, but it has ugly API so i'm writing some helper functions to hide ugliness from lisp. i can use the library from C without much thinking, but when loading it into lisp i have to say: (load-foreign '("artm-wrap.o" "libmedia1.a" "libmedia2.a") :libraries '("-lc" "-L/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/" "-lgcc" "-lz")) i guess the libmedia uses some gcc-specific features on linux which require linking with gcc... i'm not sure how this would have looked in allegrocl, but the issue might be the same, no? -- gr{oe|ee}t{en|ings} artm

2 4

[cells-devel] PortaGlut 1.0
by Kenny Tilton 24 Feb '04

24 Feb '04

Raistlin, Sorry, I tried BCCing cells-devel when I posted the errata below to comp.lang.lisp, but did not notice that they never appeared. Raistlin Magere wrote: > Ok I have played with portaglut only a few minutes so nothing too > insightfull: > I load the program by running first "glbind.lpr" [no errors here] and > then "opengl-ffi.lpr" which returns the following error > > Error: (SETF NIL) does not have a function definition > [condition type: SIMPLE-ERROR] I have no idea what is going on with that. See errata for my fulminations againt the project manager, which is dandy but can be a total PITA sometimes. > > > the options are to skip loading uffi.lpr (which was already loaded by > glbind) or to skip loading opengl-ffi, aborting the loading of > uffi.lpr seems to solve the problem. Sh*t, I kept telling myself to delete glbind.lpr. That was an old name for it. Just use opengl-ffi.lpr. I am totally sorry for wasting your time by neglecting to delete that file. > > In fact deleting from opengl-ffi the line > :projects (list (make-instance 'project-module :name > "\\dvx\\uffi\\uffi")) > allows the loading of the two projects in succession without any > problem, by the way I need to run the two project as opengl-ffi > although requiring glbind doesn't automatically load it. > > I then run (ogb::lesson-14) and get the following error > > Error: Attempt to call #("glClearDepth" 1669795401 0 2 1669795401) for > which the definition has not yet been (or is no longer) loaded. > [condition type: SIMPLE-ERROR] That was in the errata. I need to add a wrapper for uffi::load-library which checks that the library exists. uffi does not. Find the hard-coded loads of opengl32 and glu32 and change to match your configuration. > > The program does manage to create a new window titled "NeHe's OpenGL > Framework" however I only see the outline of it and nothing else. > > By the way I got an error similar to the one above when I tried to > load a dll I had made for test purpose to learn to use uffi or > acl-ffi, the loading of the dll went fine and lisp said library loaded > however when trying to call the function I would get the same error (I > think even the same numbers) but with the name of the function I had > tried to call. I then gave up on ffi and uffi - though I still need to > use some c code. Maybe this will help me out also with my work. Well, it might be different, but I can help with that, too. The first thing to do is what I will do to fix my stuff: (let ((dll-path "whatever")) (assert (probe-file dll-path)) (uffi:load-library dll-path)) If that works, well, what C compiler are you using? Using VC++, I have to do two things: wrap the C functions in extern "C" {} declarations /and/ list each function name in a .DEF file included in the source for the VC++ project. I /think/ naming the C file is an alternative to wrapping the function in the extern form. The FTGLFromC.cpp and the def file I sent illustrate the above. Sorry again I botched sending the errata (below). kenny Kenny Tilton wrote: > OK, 3D-lovers, the (model) matrix is now your oyster (if UFFI loves you): > > http://www.tilton-technology.com/cellophane.html > Just installed from ZIP. Errata: 1. In dvx/lib there is a freeglut.zip from which freeglut.dll should be extracted. Won't happen again. 2. Look for load of freeglut.dll from hard-coded "D:/dvx/lib". 3. Also look for hard-coded loads of opengl32 and glu32 from "/winnt". That's "/windows" on other wins, lord knows what on other oses. The bad news here is that uffi:load-library seems not to mind at all if it is asked to load a non-existent library, so the first sign of trouble is a runtime erorr something like "glClearColor? what the hell is that?" 4. ACL users: because the handling of the project files is such a phenomenal PITA, I get "opengl-bindings" package not found because after I change the defpackage inside the LPR (it's just source) to: (defpackage :opengl-bindings...) ACL changes it back to common-graphics whenever it feels like it. :) I would tell you the fix if I knew one, but in the past I just turn a few hundred monkeys trying things at random until it works, and then I never know which monkey fixed it nor certainly what they did to fix it. kenny -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application

1 0

RE: [cells-devel] PortaGlut 1.0
by Raistlin Magere 24 Feb '04

24 Feb '04

Ok I have played with portaglut only a few minutes so nothing too insightfull: I load the program by running first "glbind.lpr" [no errors here] and then "opengl-ffi.lpr" which returns the following error Error: (SETF NIL) does not have a function definition [condition type: SIMPLE-ERROR] the options are to skip loading uffi.lpr (which was already loaded by glbind) or to skip loading opengl-ffi, aborting the loading of uffi.lpr seems to solve the problem. In fact deleting from opengl-ffi the line :projects (list (make-instance 'project-module :name "\\dvx\\uffi\\uffi")) allows the loading of the two projects in succession without any problem, by the way I need to run the two project as opengl-ffi although requiring glbind doesn't automatically load it. I then run (ogb::lesson-14) and get the following error Error: Attempt to call #("glClearDepth" 1669795401 0 2 1669795401) for which the definition has not yet been (or is no longer) loaded. [condition type: SIMPLE-ERROR] The program does manage to create a new window titled "NeHe's OpenGL Framework" however I only see the outline of it and nothing else. By the way I got an error similar to the one above when I tried to load a dll I had made for test purpose to learn to use uffi or acl-ffi, the loading of the dll went fine and lisp said library loaded however when trying to call the function I would get the same error (I think even the same numbers) but with the name of the function I had tried to call. I then gave up on ffi and uffi - though I still need to use some c code. Maybe this will help me out also with my work. Raistlin _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus

1 0

[cells-devel] CelloGlut AOK
by Kenny Tilton 24 Feb '04

24 Feb '04

Man, this was easy. I now have several demos including the wildest one running under what I call CelloGlut, which just adds Cells and the bulk of the Cello gui. No new libraries such as FTGL or ImageMagick. The downside is that only the two stroke fonts are available (one mono-spaced, one variable) and they look like hell, but this is just to have an intermediate porting step (not that some folks would not be able to make use of CelloGlut) and I believe a little opengl work would fix the stroke fonts up a bit. A little cosmetic work tomorrow and I can make another release. kenny -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application

1 0

[cells-devel] portaglut 1.0
by Kenny Tilton 24 Feb '04

24 Feb '04

A mail message to y'all bounced on a bad address, and the bounce won't show me the original. But I did post a similar to cll: OK, 3D-lovers, the (model) matrix is now your oyster (if UFFI loves you): http://www.tilton-technology.com/cellophane.html Under "Early Cello Screen Shots", first paragraph, Portaglut (in the form of dvx.ZIP, lies behind the "bindings" link. I just built and ran via ACL LPRs and ACL using ASDF. See "build.lisp" now at top level in new DVX directory, replacing DEV which was bad for Linux/Unix. Build.lisp was in the cello directory. The test function, as you will see in build.lisp, is (ogb::lesson-14). The string "NeHe etc " swigns around in 3D. Hit esacpe to quit. This will be quite a Hello,World. It involves successfully building bindings to opengl as well as FreeGlut, and it shows callbacks Lisp->C->Lisp work (and loading shared libs). Note that this does not involve Cells, any Cello gui, FTGL, or ImageMagick. It also has hard-coded DLL locations and more out the wazoo. Seek and destroy. btw, lesson-14 used to have code in there that used the glut bitmap fonts as well as the glut stroke fonts now in there. those calls brought down freeglut and the Lisp ide, so I yanked them. caveat: Originally developed/tested on XP/ACL62, then ported to NT/ACL501 to resolve a problem there. I have not yet swapped this back to my ACL62/XP setup to make sure it still works there, but I will tonight sometime. caveat: To make UFFI work under ACL501 I snuck a conditionalization onto one place where the ACL62-only :strings-convert option was used. invitation: questions, comments, fixes for new environments. however: regrettably, I myself won't have time to come up with fixes for new environments. peace, love, and the z-axis, kenny -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application

1 0

[cells-devel] Re: ANNC: Lisp FFI tools with OpenGL+Glut samples
by Kenny Tilton 24 Feb '04

24 Feb '04

Kenny Tilton wrote: > OK, 3D-lovers, the (model) matrix is now your oyster (if UFFI loves you): > > http://www.tilton-technology.com/cellophane.html > Just installed from ZIP. Errata: 1. In dvx/lib there is a freeglut.zip from which freeglut.dll should be extracted. Won't happen again. 2. Look for load of freeglut.dll from hard-coded "D:/dvx/lib". 3. Also look for hard-coded loads of opengl32 and glu32 from "/winnt". That's "/windows" on other wins, lord knows what on other oses. The bad news here is that uffi:load-library seems not to mind at all if it is asked to load a non-existent library, so the first sign of trouble is a runtime erorr something like "glClearColor? what the hell is that?" 4. ACL users: because the handling of the project files is such a phenomenal PITA, I get "opengl-bindings" package not found because after I change the defpackage inside the LPR (it's just source) to: (defpackage :opengl-bindings...) ACL changes it back to common-graphics whenever it feels like it. :) I would tell you the fix if I knew one, but in the past I just turn a few hundred monkeys trying things at random until it works, and then I never know which monkey fixed it nor certainly what they did to fix it. kenny

1 0

[cells-devel] PortaGlut 1.0
by Kenny Tilton 24 Feb '04

24 Feb '04

A mail message to y'all bounced on a bad address, and the bounce won't show me the original. But I did post a similar to cll: OK, 3D-lovers, the (model) matrix is now your oyster (if UFFI loves you): http://www.tilton-technology.com/cellophane.html Under "Early Cello Screen Shots", first paragraph, Portaglut (in the form of dvx.ZIP, lies behind the "bindings" link. I just built and ran via ACL LPRs and ACL using ASDF. See "build.lisp" now at top level in new DVX directory, replacing DEV which was bad for Linux/Unix. Build.lisp was in the cello directory. The test function, as you will see in build.lisp, is (ogb::lesson-14). The string "NeHe etc " swigns around in 3D. Hit esacpe to quit. This will be quite a Hello,World. It involves successfully building bindings to opengl as well as FreeGlut, and it shows callbacks Lisp->C->Lisp work (and loading shared libs). Note that this does not involve Cells, any Cello gui, FTGL, or ImageMagick. It also has hard-coded DLL locations and more out the wazoo. Seek and destroy. btw, lesson-14 used to have code in there that used the glut bitmap fonts as well as the glut stroke fonts now in there. those calls brought down freeglut and the Lisp ide, so I yanked them. caveat: Originally developed/tested on XP/ACL62, then ported to NT/ACL501 to resolve a problem there. I have not yet swapped this back to my ACL62/XP setup to make sure it still works there, but I will tonight sometime. caveat: To make UFFI work under ACL501 I snuck a conditionalization onto one place where the ACL62-only :strings-convert option was used. invitation: questions, comments, fixes for new environments. however: regrettably, I myself won't have time to come up with fixes for new environments. peace, love, and the z-axis, kenny

1 0

[cells-devel] PortaGLUT: FTGLFromC.cpp: Cannot load C++ object file into ACL6.2
by Frank Goenninger 23 Feb '04

23 Feb '04

Hi all: I tried to create a shared lib from the file FTGLFromC.cpp and succeeded in doing so. But when trying to load the new libftglint.so (for "FTGL Interface") I see the following error in ACL62Trial on Linux: ; Loading /home/frgo/projects/cello/ftgl-int/libftglint.so.1 Error: Attempt to take the value of the unbound variable ^?ELF^A^A^A ... [condition type: UNBOUND-VARIABLE] So I decided to check if the lib is valid in its format. I put togehter a simple main.cpp file: --X-- #include <stdio.h> #include <dlfcn.h> #include "FTGLTextureFont.h" #include "FTTextureGlyph.h" #define LIBFTGLINT "/home/frgo/projects/cello/ftgl-int/libftglint.so.1" #define FONT "Verdana" extern "C" { int main( int argc, char **ppcArgv ) { int nRC = 0; void *pvHandle = NULL; char *pcError = NULL; /* FTGLTextureFont *psTextureFont = NULL; */ void *psTextureFont = NULL; typedef void* (*fgcTextureMakeSymPtr)(const char *); fgcTextureMakeSymPtr fgcTextureMakeFRGO = NULL; void *fgcTextureMake = NULL; pvHandle = dlopen( LIBFTGLINT, RTLD_LAZY ); if( pvHandle == NULL ) { fprintf(stderr, "%s !\n", dlerror()); nRC = 1; } if( nRC == 0 ) { fgcTextureMake = dlsym( pvHandle, "fgcTextureMake" ); if(( pcError = dlerror()) != NULL ) { fprintf( stderr, "%s !\n", pcError ); nRC = 1; } if( nRC == 0 ) { fgcTextureMakeFRGO = (fgcTextureMakeSymPtr) fgcTextureMake; psTextureFont = (*fgcTextureMakeFRGO)( FONT ); printf("psTextureFont = %x\n", psTextureFont ); } dlclose( pvHandle ); } return nRC; } } /* extern "C" */ --X-- and when running the resulting little program I actually get a valid address for the texture font pointer. This clearly shows that building the shared lib succeeded. In ACL62Trial I get this error whenever I try to load a shared lib that has some C++ object files in it. I double checked on the right compile options and flags... Any ideas? I couldn't find anything on Franz's WWW pages and also googling didn't reveal something. Thx for feedback! Regards, Frank

2 1

[cells-devel] PortaGLUT
by Kenny Tilton 23 Feb '04

23 Feb '04

After reflecting on Raistlin's input, and my previously expressed interest in breaking Cello up into discrete components, I suddenly recalled that the nehe-14.lisp demo did not even require Cells. It was a pure test of Lisp+UFFI+Freeglut+OpenGL. That alone would be useful to many, so I think I will tackle that when I get back from the gym. I will test it under ACL62 and ACL501, as well as whatever LW and Trial versions will run it, then make it available by FTP. Sorry for spamming the Cells list with this, but we still do not have a second working platform, so Cello does not yet exist. By the end of the week this will be resolved. Hell, if we get PortaGlut working on other platforms I will apply for a new project on common-lisp.net. kt -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application

1 0

[cells-devel] Re: Cello - Errors when running on ACL5.0.1
by Kenny Tilton 23 Feb '04

23 Feb '04

Raistlin Magere wrote: > Hi, > I tried to run Cello through the cloucell.lpr (after having > apprpriately modified the hard-links); it complains about the lack of > a uffi.lpr file, as I already have uffi installed on my image > {(asdf:operate 'asdf:load-op :uffi)} I just removed the link to it in > the opengl-ffi.lpr {i.e. I remove the line :projects (list > (make-instance 'project-module :name "..\\uffi\\uffi"))} Puzzling how that got left out. Current one is attached, but it just builds UFFI the way ASDF would. I am perty sure I still have acl501 on my old NT box. I will fire that up later and see if I can make that port. > > > However when I then run cloucell I get the list of errors that enclose > at the end of this message. > As you can see most errors regard the fact that unsigned-integer is > not of the right type. > There are also some other errors though; mainly > Part4 and Part11 about missing files, > Part5 about a function requiring exactly 9 parameters and being passed > only 8 > Part10 about a missing class (though this could be due to previous > errors) > Part8 and Part9 warnings about free variable reference (not a big deal) > Part12 about While --- this error has been in cells for a very long > time there is only 1 while which needs to be replaced with either an > if call or with a cl::while when running cells in acl5.0.1 > The problem is in dataflow-management.lisp and the line is > (while (and *sw-pending* > (not *sw-looping*)) > #+dfdbg Now that I am a looper I can just use that. > > > Just as a side note I am using ACL5.0.1 (which could explain problem > about Part5 as maybe the functions requirement have changed from 5.0.1 > to 6.2) also in order to get Uffi to run in 5.0.1 the line: > :strings-convert nil) in def-function from the file "functions.lisp" > of the uffi package, had to be removed; > has such parameter doesn't exist in 5.0.1 while is present in 6.2 -not > sure if this can explain the unsigned-integer errors. Ah, yes, vague memory on that. Thx for the reminder. btw, did you grab the latest UFFI? Hopefully it is backward compatible to acl501 (assuming it has been updated for acl62.) > > > Maybe I should try running it again by using your uffi.lpr file (I > don't have it though). > > Thanks, > raistlin Thank you! So much for the "null port". :) I should have known better. > > > Here are the errors they are all marked by ---Errors Partx--- where x > is the number I refered to in the above message. > > ---Errors Part1--- > ; While compiling GL-MATERIALFV in > c:\Cello-Dev\cello\opengl-ffi\gl-functions.lisp: > Warning: a direct call of `(glMaterialfv LANGUAGE C)' cannot be > compiled in-line because the argument type `UNSIGNED-INTEGER' is not > either a one-dimensional simple-array or one of: :FOREIGN-ADDRESS > :LISP FIXNUM INTEGER SINGLE-FLOAT DOUBLE-FLOAT :SINGLE-FLOAT-NO-PROTO > SIMPLE-STRING CHARACTER. I am trying to remember if that is necessarily bad, or if I get them myself. > ---Errors Part4--- > Cannot find c:\Cello-Dev\cello\opengl-ffi\nehe-14.lisp. Will skip and > continue compiling project. I forgot that was pulled in my the bindings project when I was downsizing the zip to get it thru. Anyway, looks like it needs work, it exits and takes down ACL just after opening the window. You guessed right, it is a throwaway, but maybe I should bring it back since it is a nice half-port: it only requires freeglut (or some glut). Anyway, the first thing I will do is get all this sorted out /and/ put the next zip up on tilton-technology with a password (unless I can figure out SSH again and just FTP it up to the common-lisp project. but then I also have to figure out the GnuPG thing because they want me to sign this stuff. :() > > > ---Errors Part5--- > ; While compiling CELLS-TIME-REPORT in c:\Cello-Dev\cells\debug.lisp: > Warning: EXCL::TIME-REPORT should be given exactly 9 arguments. It > was given 8 arguments. > Problem detected when processing > (EXCL::TIME-REPORT CPU-GC-USER CPU-GC-SYS ...) > inside (BLOCK CELLS-TIME-REPORT (TRC "cpu-gc-user" CPU-GC-USER) ...) > inside (PROGN (BLOCK CELLS-TIME-REPORT (TRC "cpu-gc-user" CPU-GC-USER) > ...)) Omigod! That is totally ACL specific. I have to feature that out with +ACL62 or even just lose it. > > > ---Errors Part6--- > ; While compiling MAGICK-CONTRAST-IMAGE in > c:\Cello-Dev\cello\magick-wand.lisp: > Warning: a direct call of `(MagickContrastImage LANGUAGE C)' cannot be > compiled in-line because the argument type `UNSIGNED-INTEGER' is not > either a one-dimensional simple-array or one of: :FOREIGN-ADDRESS > :LISP FIXNUM INTEGER SINGLE-FLOAT DOUBLE-FLOAT :SINGLE-FLOAT-NO-PROTO > SIMPLE-STRING CHARACTER Looks like this is our only hard error. While playing with nehe-14 just now I did a full build and got no errors on anything. > ---Errors Part8--- > ; While compiling (:INTERNAL (:INTERNAL MAKE-LIGHTING 1) 0) in > c:\Cello-Dev\cello\lighting.lisp: > Warning: Free reference to undeclared variable *MGW-ZNEAR* assumed > special. > Warning: Free reference to undeclared variable *MGW-ZFAR* assumed > special. Looks familiar. I will fix (or determine if it is an ASDF dependency thing). > ---Errors Part10--- > Error: No class named: EXCL::STRUCTURE-EFFECTIVE-SLOT-DEFINITION. > [condition type: PROGRAM-ERROR] My bad. > > > ---Errors Part11--- > Cannot find c:\Cello-Dev\cello\load-music.lisp. Will skip and > continue compiling project > Cannot find c:\Cello-Dev\cello\visual-music.lisp. Will skip and > continue compiling projec > Cannot find c:\Cello-Dev\cello\vm-test.lisp. Will skip and continue > compiling project. Oy, just lose those (or better, just wait till next distro this PM). Cello does not play (yet!). > > > ---Errors Part12--- > While compiling these undefined functions were referenced: CELLS::WHILE. I'll nail it. Thx, sorry for the avoidable errors, new distro coming ASAP (but I am hitting the gym first). kenny -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application ;; -*- lisp-version: "6.2 [Windows] (Jun 26, 2002 11:39)"; common-graphics: "1.389.2.105.2.14"; -*- (in-package :common-graphics-user) (defpackage :common-lisp-user (:export)) (define-project :name :uffi :application-type (intern "Standard EXE" (find-package :keyword)) :modules (list (make-instance 'module :name "src\\package.lisp") (make-instance 'module :name "src\\primitives.lisp") (make-instance 'module :name "src\\objects.lisp") (make-instance 'module :name "src\\aggregates.lisp") (make-instance 'module :name "src\\functions.lisp") (make-instance 'module :name "src\\strings.lisp") (make-instance 'module :name "src\\libraries.lisp") (make-instance 'module :name "src\\os.lisp")) :projects nil :libraries nil :distributed-files nil :project-package-name :common-lisp-user :main-form nil :compilation-unit t :verbose nil :runtime-modules '(:cg :drag-and-drop :lisp-widget :multi-picture-button :common-control :edit-in-place :outline :grid :group-box :header-control :progress-indicator-control :common-status-bar :tab-control :trackbar-control :up-down-control :dde :mci :carets :hotspots :menu-selection :choose-list :directory-list :color-dialog :find-dialog :font-dialog :string-dialog :yes-no-list-dialog :list-view-control :rich-edit :drawable :ole :www :aclwin302) :splash-file-module (make-instance 'build-module :name "") :icon-file-module (make-instance 'build-module :name "") :include-flags '(:compiler :top-level :local-name-info) :build-flags '(:allow-debug :purify) :autoload-warning t :full-recompile-for-runtime-conditionalizations nil :default-command-line-arguments "+cx +t \"Initializing\"" :old-space-size 256000 :new-space-size 6144 :runtime-build-option :standard :on-initialization 'default-init-function :on-restart 'do-default-restart) ;; End of Project Definition

1 0

Re: [cells-devel] PortaCello 1.0
by Kenny Tilton 23 Feb '04

23 Feb '04

Gary Klimowicz wrote: >I was planning on doing some development on win32, as that's how my >system is set up right now. > >I can be flexible about which Lisp you want me to port it to. I've been >using ACL, but am amenable to working on whatever you feel you are most >in need of. I want to help and am not too fussy about how. > >Make a wish. :-) > > Uh-oh, I sent it last night, 11pm NYC time. I think I'll just put it up on my web site, because most people have had trouble getting it via email. Plz confirm you did not receive and I will do that. As for making a wish, that is very generous of you. It would be fine if you just played the part of user (vs. porter) and helped me figure out what documentation or examples to write. (I always prefer examples, and those are easier for me to pull together.) If you are really interested in porting, then Corman is the one implementation remaining to cover. CLisp (I think!) does not handle callbacks from C, which we need to use Freeglut. Hey, who else is working on Corman? So many have asked for distros, I have lost track. :) kenny -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application

2 4

Re: [cells-devel] PortaCello 1.0
by Kenny Tilton 23 Feb '04

23 Feb '04

Gary Klimowicz wrote: >I did get the files via e-mail last night; that worked fine. > >Let me take a look at Corman and/or Clisp. It does look like the Clisp >FFI has a way of calling back from C to Lisp, but it might not be >dynamic enough to support the kinds of callbacks you need. > >I also like the idea of docs/examples help; given the rustiness of my >developer skills, I could be over my head on porting. > well then, since you have the "reference platform" acl62/win, you might try the "null port" and just see if you can get it to run over there. if so, track down the function make-starter-w and you'll see something like this: (defun make-starter-w (&key (offset (mkv2 0 0))) (make-instance 'window :md-value (list ;(tu-geo) ;(imagick-test) ;(ftgl-test) ;(make-widgets) (light-panel) ;(cloucell) ) :display-continuous t ...etc I am pretty sure the source as shipped had most of those list items commented out. de-comment to activate any of the various demos. If you activate them all expect a healthy delay when the window opens since all the structure gets built before you see the window the first time. Expect a memory leak forcing you to quit ACL if you play around very long. Then you might want to try playing with the demos to see what changes what. Ideally you have a project in mind we could work on. I like the Black Book approach to documentation, which presumes you have some real world task to do and shows how to get it done all in a few pages, no matter how many different activities are involved. But step one is to achieve the null port. Lemme know how it goes. kenny -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

cells-devel February 2004