attempt arm64 mac build

.github/workflows/build.yml

@@ -64,9 +64,9 @@ jobs:
     runs-on: macos-12
     strategy:
       matrix:
-        python-version: ['3.10.5', 'pypy-3.9'  ]
+        python-version: ['3.10.5']
+        # Requires universal2 build of python, which we get if we ask for 3.10.5 x86! Pypy not available in universal2
     steps:
-      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
       - uses: actions/checkout@v2
         with:
           submodules: recursive
@@ -74,12 +74,10 @@ jobs:
       - name: Setup Python
         uses: actions/setup-python@v2.2.2
         with:
-          # Version range or exact version of a Python version to use, using SemVer's version range syntax.
           python-version: ${{ matrix.python-version }}
-          # The target architecture (x86, x64) of the Python interpreter.
           architecture: x64
 
-      # Runs a set of commands using the runners shell
+      # Only build raylib for arm64 (although we could make a fat universal2 binary by asking for x86_64 as well)
       - name: Build raylib
         run: |
           cd raylib-c
@@ -92,6 +90,11 @@ jobs:
         run: |
           sudo cp physac/src/physac.h /usr/local/include/
           sudo cp raygui/src/raygui.h /usr/local/include/
+
+      # Name defaults to universal2 and it technically is, but it wont run on x86_64 because we didnt build raylib for that
+      # so symbols are missing.  So we override name to arm64.  Why don't we make a working universal2 wheel?  Because
+      # I'd rather have a separate x86_64 that I can test, and I want it to work on 10_15 but I'm not sure a 'macosx_10_15_universal2' is valid
+      # given that there is no SDK for universal until macosx_11_0
       - name: Build raylib-python-cffi
         run: |
           python -m pip install --upgrade pip