Repository navigation
Problems with the resources folder and some errors #1
Description
Hey, I just made a GitHub account for the sole reason of making this issue. I tried compiling your game, but I've ran into some problems, some solved, some unsolved.
Zero documentation on how to install this game
I probably wouldn't have made this issue if it weren't for the absence of any documentation on how to build this game from source. So I assumed cargo install --path . is what I had to run to get this game installed.
The resources directory
Why is it when I compile this game, multiple instances of the resources folder are scattered across my filesystem? This game should just install the binary and the resources into one directory. For example, you could put the binary in /usr/local/bin and have the resources in ~/.config/callofferris. To make matters worse, all the instances of the resources folder are empty.
Errors
Even if I copy the contents of the resources directory from this Git repo unto ~/.cargo/bin/resources, I still get this error:
Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }
And if I run target/release/call_of_ferris:
thread 'main' panicked at 'attempted to leave type `platform::platform::x11::util::input::PointerState` uninitialized, which is invalid', /rustc/cb75ad5db02783e8b0222fee363c5f63f7e2cf5b/library/core/src/mem/mod.rs:659:9
Activity
Andy-Python-Programmer commentedon Apr 5, 2021
Thanks for reporting the issue! I will try to document things better but
cargo install --path .is how one should be able to install CallOfFerris.Issues about the resources directory: Appears that this issue is in ggez and its not very actively developed. I am looking forward for porting this to either amethyst or bevy. RFC for the engine as they both are a lot actively developed. I am just waiting for amethyst port to finish. Other then that you can run the game using
cargo runin the project directory.Let me know if the game also does not work using
cargo runTarnadas commentedon Apr 7, 2021
see ggez/ggez#843 and rust-windowing/winit#1773
It's an issue with winit dependency and ggez needs to update to that. It's already working on ggez' devel branch, but devel is currently not compiling and also this crate needs to be updated to be compatible with new ggez version.
As long as it is not fixed, you can use rustc 1.47