Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Should this run on Ubuntu as well, or...?

A topic by Gmr_Leon created Jan 25, 2024 Views: 116 Replies: 3
Viewing posts 1 to 2
(+1)

Hey there! I was looking through some open source game lists and came across this, and in turn the rest of your work. I started to give them a try but I've hit a snag. When I download the zip from here and unzip it and try to run the executable on Ubuntu Mate 22.04.3 (Jammy Jellyfish)...Nothing happens. Hardware specs are a laptop with an i5-2450M and AMD Radeon HD7670M, so an older machine, which may be the catch, I'm guessing?

Checked that it was set as executable and tried to run it via terminal, but it only says, "Illegal Instruction" or "Illegal Instruction (core dumped)" (changing depending on if I try to run it with apostrophes or not if memory serves). I tried to check if I was missing some dependencies via the ldd command, but I'm not too familiar with Linux, so I'm not sure if I may be missing some or not. I checked the package manager and searched for most of those listed and it looked like many of them were installed, but that may be the wrong approach.

Thanks for any advice!

Developer (1 edit) (+1)

Thanks for trying. I would have expected the build artifact to run on that platform's version, but it seems a separate compilation is required. Someday someone might figure out Flatpaks, but for now you could try to download/clone the repository and run install.sh. That should take care of everything.

Also, feel free to come aboard the Colourship for a chat or support.

(+1)

Appreciate the reply! I gave that a try and after sorting out some of the odds & ends to run install.sh, it errors out with:

"/usr/bin/ld: cannot find /home/[username]/.../heXon/Dry/lib/libDry.a: No such file or directory"

If I understand right, install.sh should be pulling that alongside the other necessary stuff from the Dry repo, right? I checked my local files, and as expected, it's not there, so I partly understand why it's failing, but not sure what's still asking for that file nor why it creates the lib directory but doesn't pull/produce the relevant file. In any event, I've learned some more Linux stuff, sort of, so if nothing else there's that. 馃槄

I'm guessing my best bet may be to try switching to Linux Mint and trying it in the same environment, which tbh I've been considering switching to Linux Mint at some point anyway.

Developer(+1)

Don't blame yourself, it's a mess. I'm not quite a neckbeard myself. :)

The script is supposed to pull and build the engine, not err. But since it looks like you'll be switching to Mint anyway, I guess there's no immediate hurry to solve it, and I'll just assume you can  simply unpack on your new platform.