Wow, it runs! I will play it tonight.
sinofp
Creator of
Recent community posts
The log is:
==> Deploy log started on 2022.11.09 22:42:38
==> Performing warm boot.
-> Runtime directory is D:/bin/
-> Resource directory is D:/bin/
==> Running boot hooks.
==> Reloading foreign libraries.
-> Loading foreign library #<LIBRARY LIBSDL2-TTF>.
-> Loading foreign library #<LIBRARY LIBFFI>.
-> Loading foreign library #<LIBRARY LIBSDL2-IMAGE>.
-> Loading foreign library #<LIBRARY LIBSDL2>.
-> Loading foreign library #<LIBRARY OPENGL>.
==> Launching application.
I found that is the same as the command line output of the previous version, so there’s no need to define an environment variable to see the log.
Sorry, I really want to try this game, but I can’t. I tried various ways to install chickadee, but I failed in every way. That library wants a develop version of Guile even though I build Guile from the source. I also tried Guix, at first it seems to install chickadee successfully but there is no chickadee executable after installation. Then I tried the Guix System’s QEMU image but it’s too slow to use. I guess I have to give up. The Guile tooling is too obscure for me.
It won’t error from the beginning, but once I input the colon number, they all pop up a black window and output the same error as before.
debugger invoked on a SDL2::SDL-RC-ERROR in thread
#<THREAD "SDL2 Main Thread" RUNNING {1003152D53}>:
SDL Error (-1): That operation is not supported
The current thread is not at the foreground,
SB-THREAD:RELEASE-FOREGROUND has to be called in #<SB-THREAD:THREAD "main thread" RUNNING {1000558083}>
for this thread to enter the debugger.
^C
debugger invoked on a SB-SYS:INTERACTIVE-INTERRUPT in thread
#<THREAD "main thread" RUNNING {1000558083}>:
Interactive interrupt at #x7FE6D76287FB.
Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [EXIT ] Exit.
1: [ABORT] Exit from the current thread.
("bogus stack frame")
0]
So, the problem resides in the sketch library. I wonder if that library works on Windows. I think Windows is the ultimate platform for distributing binaries.
Firefox depends on SDL2, I can open Firefox, so I think my SDL2 works fine.
I’m using WSL, according to their blog, WSL includes Direct3D, and I can find the .so files.
I’m not sure. glxinfo | grep OpenGL
shows the following output, so I think it supports OpenGL 4.5.
OpenGL vendor string: Mesa/X.org
OpenGL renderer string: llvmpipe (LLVM 14.0.6, 256 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 22.2.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5 (Compatibility Profile) Mesa 22.2.2
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
Running glxgears
can show me three rotating gears.
Thank you, now the game can pop up a black screen. The console said:
==> Performing warm boot.
-> Runtime directory is /home/unv/rhombihexadeltille-game/
-> Resource directory is /home/unv/rhombihexadeltille-game/
==> Running boot hooks.
==> Reloading foreign libraries.
-> Loading foreign library #<LIBRARY LIBSDL2-MIXER>.
-> Loading foreign library #<LIBRARY LIBSDL2-TTF>.
-> Loading foreign library #<LIBRARY LIBFFI>.
-> Loading foreign library #<LIBRARY LIBSDL2-IMAGE>.
-> Loading foreign library #<LIBRARY LIBSDL2>.
-> Loading foreign library #<LIBRARY OPENGL>.
==> Launching application.
debugger invoked on a SDL2::SDL-RC-ERROR in thread
#<THREAD "SDL2 Main Thread" RUNNING {10032B1793}>:
SDL Error (-1): That operation is not supported
The current thread is not at the foreground,
SB-THREAD:RELEASE-FOREGROUND has to be called in #<SB-THREAD:THREAD "main thread" RUNNING {10005B8083}>
for this thread to enter the debugger.
^C
debugger invoked on a SB-SYS:INTERACTIVE-INTERRUPT in thread
#<THREAD "main thread" RUNNING {10005B8083}>:
Interactive interrupt at #x7FC5AFD807FB.
Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [EXIT ] Exit.
1: [ABORT] Exit from the current thread.
("bogus stack frame")
0]
I don’t know what is wrong. The error message is arcane to me. :(