On Mon, May 11, 2009 at 10:27 PM, Justin Heyes-Jones <[email protected]>wrote:
> That helps. Ok the file is there, it has read permissions for all groups. > A couple of requests: >From the debugger, could you print *autoload-directory-defaults*? Just type, 0] *autoload-directory-defaults* Also, could you print the backtrace? 0] backtrace Finally, I'm still curious what 0] (truename "/path/to/image/file") returns. This may help. This is the syntax I use to make a path in a game I'm > working on, that works on linux (although I haven't tried exporting it > as a stand alone so maybe not). > > (sdl:create-path "pongbgnd.bmp" cl-user::*bmp-path*) > I used to specify paths manually, but found that quite tedious, even with CL's built-in pathname facilities. What I currently do is specify some directory to be a root graphics directory, somewhat like your *bmp-path* above. I then use FAD to recursively iterate over the directory, constructing pathnames to each image as I go down the directory structure. I create a mapping from pathnames to directories, so a file #p"/home/elliott/game/disp/foo/bar.bmp" would map to the symbol 'foo-bar (assuming #p"/home/elliott/game/disp" is the root directory). I then create and load my images with calls like (make-instance 'image :name 'foo-bar). I'm guessing something is going wrong in the image autoloading code. Unfortunately, I've never seen this bug in person, despite developing on two completely isolated linux machines, so I don't have any particular insight as to what is going wrong here. The only other thing to do would be to try compiling from source, but I feel I've already asked too much from you. Thanks again for the assistance. -- Elliott Slaughter "Don't worry about what anybody else is going to do. The best way to predict the future is to invent it." - Alan Kay
_______________________________________________ application-builder mailing list [email protected] http://www.lispniks.com/mailman/listinfo/application-builder
