cells-devel February 2004

cells-devel@common-lisp.net

5 participants
36 discussions

[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

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

23 Feb '04

Speaking of "where is help needed", depending on one's skill set, here are some that I have been deferring: These two would be good for a strong C and esp. win32 programmer: -- Freeglut/win32: calling glutMainLoop leaves the app taking 100% of CPU. This is weird because win32 apps are supposed to wait until their windowproc gets called. Possibly they are failing to handle repaint events (in which case I think you just keep getting called again and again) or they are doing something to cause windows to send the app events non-stop, such as by invalidating the window after handling each paint event to cause another to be sent straight away. -- Freeglut/win32: before the current release I had code which called glutMainLoopEvent to handle one event at a time. When I resumed work on Cello under the latest FG I found that broken in some way such the I simply did not receive all the events I should. And if anyone is strong on OpenGL: -- Drawing seems mighty fast, and I have a feeling most of the bottleneck is not in the drawing in which case we shouldn't spend too much time on this, but I am sure we could get even better performance via standard OpenGL tuning techniques such as display lists. 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] FTGL dll issue
by Kenny Tilton 22 Feb '04

22 Feb '04

Thought I should mention this. I have noticed a pattern: perhaps only because of the Freeglut/win32 problem in which it pegs the cpu at 100% forcing heroic measures to stop it, often after landing in a backtrace and fixing a bug and running again I end up with an access violation on a simple call into the FTGL. Then I have to exit Lisp and come back in. Not good, obviously, and something to be addressed before not too much longer, but for now if you suddenly see something like that you might want to try bouncing the Lisp. kenny -- 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] freetype
by Kenny Tilton 21 Feb '04

21 Feb '04

Here is the FTGL web site: http://homepages.paradise.net.nz/henryj/code/ Henry looks like a Mac OS X developer. Anyway, I noticed the Freetype project and remembered, doh!, you need that, too. 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] uffi + steppin out...
by Kenny Tilton 21 Feb '04

21 Feb '04

To those who receive 'lite' distros, I also had to whack the uffi and asdf libs. cello runs against untouched copies of those, so you can just grab them from their sites. i promise we'll cut to an ftp arrangement on the next go-round, even if on my own web site. stepping out at 5:30 nyc-time for the evening. thx for all the interest. if anyone thinks they are making progress lemme know and I will stop worrying about porting and start on the missing widgets (and see why freeglut uses 100% cpu on win32). 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] FTGL "C" glue: FTGLFromC.cpp, fgc.def
by Kenny Tilton 21 Feb '04

21 Feb '04

Short and sweet. Just enough C to let Cello at the FTGL C++ libs. These files are for those not on win32. I just added this source to the FTGL win32 VC++ project. The author of FTGL has expressed an interest in this code, so maybe he will add a C interface soon and we can stop forking. An alternative I guess would be for me to make my own FTGL-C dll and link that against an unmodified FTGL static lib. I took the quick way out for now. kenny -- http://tilton-technology.com Why Lisp? http://alu.cliki.net/RtL%20Highlight%20Film Your Project Here! http://alu.cliki.net/Industry%20Application #include <assert.h> #include "FTGLBitmapFont.h" #include "FTBitmapGlyph.h" #include "FTGLPixmapFont.h" #include "FTPixmapGlyph.h" #include "FTGLTextureFont.h" #include "FTTextureGlyph.h" #include "FTGlyphContainer.h" #include "FTBBox.h" #include "FTGLPolygonFont.h" #include "FTPolyGlyph.h" #include "FTGLOutlineFont.h" #include "FTOutlineGlyph.h" #include "FTGLExtrdFont.h" #include "FTExtrdGlyph.h" extern "C" { bool __stdcall fgcSetFaceSize( FTFont* f , unsigned int faceSize , unsigned int res ) { return f->FaceSize( faceSize, res ); } float __stdcall fgcAscender( FTFont* f ) { return f->Ascender( ); } float __stdcall fgcDescender( FTFont* f ) { return f->Descender( ); } float __stdcall fgcStringAdvance( FTFont* f, const char* string ) { return f->Advance( string ); } float __stdcall fgcStringX( FTFont* f, const char* string ) { float llx,lly,llz,urx,ury,urz; f->BBox( string, llx, lly, llz, urx, ury, urz ); return llx; } void __stdcall fgcRender( FTFont* f, const char *string ) { f->Render( string ); } void __stdcall fgcFree( FTFont* f ) { delete f; } //--------- Bitmap ---------------------------------------------- FTGLBitmapFont* __stdcall fgcBitmapMake( const char* fontname ) { return new FTGLBitmapFont( fontname ); } //--------- Pixmap ---------------------------------------------- FTGLPixmapFont* __stdcall fgcPixmapMake( const char* fontname ) { return new FTGLPixmapFont( fontname ); } //--------- Texture ---------------------------------------------- FTGLTextureFont* __stdcall fgcTextureMake( const char* fontname ) { return new FTGLTextureFont( fontname ); } //--------- Polygon ---------------------------------------------- FTGLPolygonFont* __stdcall fgcPolygonMake( const char* fontname ) { return new FTGLPolygonFont( fontname ); } //--------- Outline ---------------------------------------------- FTGLOutlineFont* __stdcall fgcOutlineMake( const char* fontname ) { return new FTGLOutlineFont( fontname ); } //--------- Extruded Polygon ------------------------------------- FTGLExtrdFont* __stdcall fgcExtrudedMake( const char* fontname ) { return new FTGLExtrdFont( fontname ); } // make a new extrd ctor that takes a depth parm bool FTGLExtrdFont::FaceDepth( float new_depth ) { Depth( new_depth ); return FaceSize( this->FaceSize(), 96 ); // force new glyphs } bool __stdcall fgcSetFaceDepth( FTGLExtrdFont* f , float depth ) { return f->FaceDepth( depth ); } } DESCRIPTION 'C Interface to FTGL' VERSION 0.1 EXPORTS fgcSetFaceSize fgcStringX fgcAscender fgcDescender fgcStringAdvance fgcRender fgcFree fgcBitmapMake fgcPixmapMake fgcTextureMake fgcPolygonMake fgcOutlineMake fgcExtrudedMake fgcSetFaceDepth

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