Perhaps things are better now, but in the old days there were relative paths in the code, so e.g. for the game to be able to find the "lib" directory you needed to be running in the directory above it. I continue to do it that way.
Assuming you have a personal bin directory that appears early in your $PATH, you could put the cd and options and whatever else into a script in your bin directory. E.g. there was a time I was tracking real time played, and I used
#! /bin/bash
cd ~/angband/Angband-4.2.5/
echo "" >> ../logs/log.4.2.5
date >> ../logs/log.4.2.5
./angband
date >> ../logs/log.4.2.5
The ./angband was a symlink to src/angband. Technically I had that file in a directory of shell scripts and a symlink to it from ~/bin
Assuming you have a personal bin directory that appears early in your $PATH, you could put the cd and options and whatever else into a script in your bin directory. E.g. there was a time I was tracking real time played, and I used
#! /bin/bash
cd ~/angband/Angband-4.2.5/
echo "" >> ../logs/log.4.2.5
date >> ../logs/log.4.2.5
./angband
date >> ../logs/log.4.2.5
The ./angband was a symlink to src/angband. Technically I had that file in a directory of shell scripts and a symlink to it from ~/bin
Comment