On 2015-01-10 10:07 AM, Scott Bronson wrote: > Currently, GnuBG can ONLY be installed in /Applications. If installed > anywhere > else, it silently fails to launch. > > Is this easy to fix? Or, would GnuBG be open to patches? > > > I see two uses of absolute paths that would need to be fixed: > > - The launch script hard-codes the path: > GNUBGPATH="/Applications/Gnubg.app/Contents/MacOS" > > - The libraries are linked using absolute paths: [1] >
I make the GNUBG builds and I won't be doing it. I don't have time. I did manage to build a version years ago (with some glitches) that was relocatable. I build from MacPorts and some of the libraries we rely on also don't work well using relative paths. I changed all the paths to be relative in the binaries and then had to hack some of the libraries 9the source code that relied on absolute paths. Maybe those libraries have been changed over the years. As it stands the official binaries won't be changing unless other people wish to do it. Making it absolute with in /Applications is much simpler from a maintenance/release standpoint. -- Michael Petch GNU Backgammon Maintainer / Developer OpenPGP FingerPrint=D81C 6A0D 987E 7DA5 3219 6715 466A 2ACE 5CAE 3304 _______________________________________________ Bug-gnubg mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-gnubg
