That's what I say, you shouldn't use it like that but use symbolic links instead if you want to create some kind of "shortcuts" to the program.
If I'm not mistaken, your
ln command here should give the absolute path to the executable so when you launch the program though the symbolic link, it launch it from the real directory where the data is.
Well, of course if users start playing and launching the program command line from the other end of the file system, then... it fails. I realize that.
What I'm saying is that a double click on the executable should work, a command line from right directory or a proper link too. So IMO with that your basic-user-proof.
To be computer-guy-proof is another story indeed.
Hiura, but that defeats the whole purpose of relative paths. Isn't there a possibility to keep the working directory unchanged when using symbolic links? On Windows, a link doesn't affect the working directory by default, but you can customize it.
I would simply require the user to invoke the program in the correct directory. Generous people may provide a meaningful error message
I think
ln -s /full/path/to/my/program/exe MyShortcut
works as intended (and as on windows). Can't remember if there's another option somewhere, I'll give it a try as soon as I'm home =)