Closed kori-irrlicht closed 4 years ago
The failures are not due to anything you did, and the PR looks good to me. Also, fixing oto should be relatively easy, just have to use the same method we do for running tests. Try building it with engo.RunOptions has Headless = true. That should skip over oto and use a fake readwriteseeker instead of oto
Thanks for the help! Let me know if the headless option works!
Thanks for the hint, but I was already using the headless option and the error occurs while building the project. Would it be possible to skip the oto dependency this way? I can build it on my machine, but building it on a build server causes an error, because it can't find the alsa package required by the Linux drivers of oto.
For now, I created a workaround by forking oto and adding an empty driver, which will ignore everything. It works for me, but I'm not sure if this is the best solution overall.
The error message:
Package alsa was not found in the pkg-config search path.
Perhaps you should add the directory containing 'alsa.pc'
to the PKG_CONFIG_PATH environment variable
No package 'alsa' found
pkg-config: exit status 1
If it would help, I can also post a link to my project
I removed the fallthrough statement. Otherwise it already looked like the glfw version, so I think this should be the necessary changes to fix the compile error I received in #738
There is still another problem with the headless build: The oto dependency is causing trouble, if no drivers are installed on a build system. But I'm not sure if this should be fixed in this pull request (or even in this repository)