Hi @virusdave.

Would or is DATADIR not being set causing issues on linux?

This allows the game to be executed from anywhere, not just from the package /bin

Does that mean the program looks for datafiles relative to where it was executed?

Can you also change the commit msg to what I edited the PR title to?

Hi @virusdave.

Would or is DATADIR not being set causing issues on linux?

Not sure. I can don't have a linux box, but i can re-read the code tonight perhaps. The program has a hardcoded set of absolute and relative paths to look for its data files. On OSX, these are "normal" locations you'd expect installed programs to live, not the nix store. The relative paths in the list are based on where the CWD was when the program was executed, not where the program actually lives on the FS.

This allows the game to be executed from anywhere, not just from the package /bin

Does that mean the program looks for datafiles relative to where it was executed?

Yes, relative to the CWD when it was executed (not where the binary itself lives, which would have also solved the problem).

Can you also change the commit msg to what I edited the PR title to?

Sure, i'll do this tonight and update the PR.

@worldofpeace I've updated the commit title.

Hi @virusdave.
Would or is DATADIR not being set causing issues on linux?

Not sure. I can don't have a linux box, but i can re-read the code tonight perhaps. The program has a hardcoded set of absolute and relative paths to look for its data files. On OSX, these are "normal" locations you'd expect installed programs to live, not the nix store. The relative paths in the list are based on where the CWD was when the program was executed, not where the program actually lives on the FS.

This allows the game to be executed from anywhere, not just from the package /bin

Does that mean the program looks for datafiles relative to where it was executed?

Yes, relative to the CWD when it was executed (not where the binary itself lives, which would have also solved the problem).

So I guess it would be okay to do this for linux also?

Yes, relative to the CWD when it was executed (not where the binary itself lives, which would have also solved the problem).

So I guess it would be okay to do this for linux also?

Ok, i've removed the conditional check for darwin on this as well. I don't have a great way to check this on linux (no linux box), but perhaps i can grab a docker image or something to test it.

Yes, relative to the CWD when it was executed (not where the binary itself lives, which would have also solved the problem).

So I guess it would be okay to do this for linux also?

Ok, i've removed the conditional check for darwin on this as well. I don't have a great way to check this on linux (no linux box), but perhaps i can grab a docker image or something to test it.

I'm using NixOS so I can test for you 👍

Actually, what is the expected directory of DATADIR?
Would that be $out/share or $out/dat or is it inferred from the parent directory?

Tested on a nixos docker container and this works still.

Actually, what is the expected directory of DATADIR?
Would that be $out/share or $out/dat or is it inferred from the parent directory?

./share and ./dat (and friends) are tried relative to DATADIR.

@virusdave This worked for me. Please squash and rephrase your commit msg.

Done.

@virusdave Thanks. I'm confident we can merge this.