MacOS prebuilt nightlies, building from source?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Bogatyr
    Knight
    • Feb 2014
    • 525

    MacOS prebuilt nightlies, building from source?

    Hi,
    Are MacOS prebuilt nightlies available anywhere?

    I tried cloning from github and building according to the instructions (cd src; make -f Makefile.osx) but get a massive error spew. Is there some assumed compiler/SDK environment required? I previously did ios development a few years ago so have some random version of XCode installed.

    First error:
    CC cave.c
    In file included from cave.c:19:
    In file included from ./angband.h:18:
    In file included from ./h-basic.h:108:
    In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/ctype.h:69:
    In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_ctype.h:69:
    /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:784:2: error: Unsupported architecture
    #error Unsupported architecture
  • backwardsEric
    Knight
    • Aug 2019
    • 531

    #2
    Originally posted by Bogatyr
    Are MacOS prebuilt nightlies available anywhere?
    They're at https://github.com/angband/angband/releases . Click on the triangle next to "Assets" for the release of interest to get the link to the *-osx.dmg file.

    Originally posted by Bogatyr
    I tried cloning from github and building according to the instructions (cd src; make -f Makefile.osx) but get a massive error spew. Is there some assumed compiler/SDK environment required?
    Recent versions of Makefile.osx try to build for both the x86_64 and arm64 architectures; the latter requires fairly recent versions of Xcode (within the last year and a half or so). To only build for x86_64 and likely avoid the problems you ran into, run this:

    Code:
    cd src; make -f Makefile.osx ARCHS=x86_64

    Comment

    • Bogatyr
      Knight
      • Feb 2014
      • 525

      #3
      That make tweak did the trick, thanks. Would probably be good to add that to the building instructions at https://angband.readthedocs.io/en/la...ml#debug-build

      Comment

      • mrfy
        Swordsman
        • Jul 2015
        • 328

        #4
        Upgraded my powerbook over the weekend to a new model, with the M1 Pro chip. Only issue I've seen so far with Angband is that it now asks repeatedly (about 4 times per save or load of savefile) to access the Documents folder.

        Hitting OK 4 times seems to do the trick. Maybe it's doing it per file? I see it updated CharOutput.txt, lore.txt, mrfy (my savefile) and window.prf

        But it doesn't record the preference so it asks again 4 times on next save.

        Comment

        • Nick
          Vanilla maintainer
          • Apr 2007
          • 9647

          #5
          Originally posted by mrfy
          Upgraded my powerbook over the weekend to a new model, with the M1 Pro chip. Only issue I've seen so far with Angband is that it now asks repeatedly (about 4 times per save or load of savefile) to access the Documents folder.

          Hitting OK 4 times seems to do the trick. Maybe it's doing it per file? I see it updated CharOutput.txt, lore.txt, mrfy (my savefile) and window.prf

          But it doesn't record the preference so it asks again 4 times on next save.
          Yes, this is a known issue. Current workarounds are do what you're doing, or build yourself from source
          One for the Dark Lord on his dark throne
          In the Land of Mordor where the Shadows lie.

          Comment

          Working...
          😀
          😂
          🥰
          😘
          🤢
          😎
          😞
          😡
          👍
          👎