search

Andy-Python-Programmer / CallOfFerris

A thrilling action game where your favorite Ferris the crab and the rust mascot got guns and has taken up the duty to find evildoer languages while managing to keep itself alive. Take part in this awesome adventure and help Ferris be the best ever!
59 stars 5 forks source link

Problems with the resources folder and some errors #1

Open ghost opened 3 years ago

ghost commented 3 years ago

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
Andy-Python-Programmer commented 3 years ago

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 run in the project directory.

Let me know if the game also does not work using cargo run

ghost commented 3 years ago

Let me know if the game also does not work using cargo run

Nope. Same X11 error as before.

Tarnadas commented 3 years ago

see https://github.com/ggez/ggez/issues/843 and https://github.com/rust-windowing/winit/issues/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

rustup install 1.47
cargo +1.47 install --path .