This is indeed useful and necessary but I see several cases to handle : - Windows installation - Linux installation -> engines are in shared dir - Linux from sources -> engines are relative to Scid's exe - Mac Os installation - Mac Os from sources
So given that the engines (at least on Linux) can be present in two different directories, depending upon the way the user launches Scid, this requires a [file executable ] or [file exists ] call to check the various possibilities. Maybe the OS test is useless : simply look for toga in /usr/local/share/... and if this fails, even on windows it is not a problem at all, you know then you have to look in ScidExeDir/. Of course engines names are different from one OS to other (crafty and wcrafty.exe), which makes the code a little bit more complicated. Pascal ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Scid-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scid-users
