I have a Mac, but unfortunately for the purpose of this discussion, I treat it pretty much as a generic UNIX system and always run XBoard from the command line in a terminal (and compile and configure it by hand).
hgm wrote:
/usr/share/games is the directory that according to Debian standards programs in /usr/games should look for their data files. So the Debian package for fairymax does put the fmax.ini file that contains the move-generator tables for all of the supported variants in
/usr/share/games/fairymax/fmax.ini
It could be put anywhere, as long as the hard-coded file name in the Fairy-Max binary would be set to where it is put, through a -DINI_FILE=... compile-time option. (For Windows, for instance, it is placed in the same folder as the binary.) In fact it is even possible to use the standard Linux binary of Fairy-Max by installing it under XBoard with an extra argument in the engine command to indicate the ini file, like
fmax /anywhere/fmax.ini
I kind of dislike that solution, though, because it means you would have to specify the argument also each time you want to run Fairy-Max from the command line.
On OS X, the best "native" location is probably something like /Library/Fairy-Max/ or ~/Library/Fairy-Max. Perhaps ~/Documents/Fairy-Max, although I personally hate it when programs decide that their stuff needs to be in my documents folder.
The directory /usr/local/etc is used to store XBoard's master configuration file, (/usr/local/etc/xboard.conf), which is used to (re)define the defaults for some of the options, including the file name of the user settings file (~/.xboardrc). This is a Debian standard for packages compiled from source. (In their own binary package for XBoard they use /usr/etc/xboard.conf in stead.)
This should probably also be something like /Library/XBoard, although keeping ~/.xboardrc should be ok-ish.
What would be the best solution here, if we were to make a special compile of XBoard using default file locations tailored to Mac OS?
I think looking in /Library and ~/Library is probably the way to go, but I'll have a look (tonight, if I remember) for what we did in another project where we needed to know the the "best match" for standard filesystem locations across platforms.
OS X is like a UNIX system, but it has its (annoying) quirks.
By the way, ultimately the best solution for running XBoard on OS X would be one that doesn't require X11. I have no idea how well cross-platform GUI toolkits do these days in that department (wxWidgets might be ok, Qt I think emulates the native GUI rather than use it, GTK required X11 the last time I tried it)...