Build MacOS ARM64 binaries with GHA

[gau-nernst]

As communicated on Slack, I added workflow to build MacOS ARM64 binaries to support Apple Silicon. I downloaded the wheels and tested on my local M1. Installation worked fine and all pytest tests passed. I only tested Python 3.8-3.11, since there is no Python 3.7 MacOS ARM64 from conda. (I think no one builds Python 3.7 for MacOS ARM64? Anyway, Python 3.7 is reaching end-of-life this June so perhaps we can even stop building for Python 3.7).

This is the workflow run in my fork: https://github.com/gau-nernst/kornia-rs/actions/runs/4263731867

The Linux builds are failing because I don't have access to the Docker images.

Also, this closes #20

[edgarriba]

Amazing. @ducha-aiki can you somehow validate ?

[ducha-aiki]

@edgarriba I don't see there any wheels built, so I cannot verify. However, yes, proper Python 3.7 support is absent here, and if we can cross-compile, that would be amazing.

[gau-nernst]

@ducha-aiki If you go to my workflow run here (https://github.com/gau-nernst/kornia-rs/actions/runs/4263731867) and scroll down to the end, can you see and download the wheels (Artifact file)?

[gau-nernst]

Also, I'm thinking about using matrix to merge mac x64 and arm64 job definition. It would look like this

  macos:
    runs-on: macos-latest
    strategy:
      matrix:
        python-version: ["3.7", "3.8", "3.9", "3.10", "3.11"]
        target: ["x86_64-apple-darwin", "aarch64-apple-darwin"]
    steps:
      - uses: ilammy/setup-nasm@v1
      - uses: actions/checkout@v3
      - uses: actions/setup-python@v2
        with:
          python-version: ${{ matrix.python-version }}
          architecture: x64
      - uses: actions-rs/toolchain@v1
        with:
          profile: minimal
          toolchain: stable
          target: ${{ matrix.target }}
          override: true
      - uses: messense/maturin-action@v1
        with:
          maturin-version: latest
          command: build
          args: --target ${{ matrix.target }} --release --out dist -i python${{ matrix.python-version }}
      - name: Upload wheels
        uses: actions/upload-artifact@v2
        with:
          name: wheels
          path: dist

Would you prefer this instead? @edgarriba

The available target names for rust can be found here: https://doc.rust-lang.org/nightly/rustc/platform-support.html

[edgarriba]

Also, I'm thinking about using matrix to merge mac x64 and arm64 job definition. It would look like this

  macos:
    runs-on: macos-latest
    strategy:
      matrix:
        python-version: ["3.7", "3.8", "3.9", "3.10", "3.11"]
        target: ["x86_64-apple-darwin", "aarch64-apple-darwin"]
    steps:
      - uses: ilammy/setup-nasm@v1
      - uses: actions/checkout@v3
      - uses: actions/setup-python@v2
        with:
          python-version: ${{ matrix.python-version }}
          architecture: x64
      - uses: actions-rs/toolchain@v1
        with:
          profile: minimal
          toolchain: stable
          target: ${{ matrix.target }}
          override: true
      - uses: messense/maturin-action@v1
        with:
          maturin-version: latest
          command: build
          args: --target ${{ matrix.target }} --release --out dist -i python${{ matrix.python-version }}
      - name: Upload wheels
        uses: actions/upload-artifact@v2
        with:
          name: wheels
          path: dist

Would you prefer this instead? @edgarriba

The available target names for rust can be found here: https://doc.rust-lang.org/nightly/rustc/platform-support.html

Probably yes

[gau-nernst]

@edgarriba I have updated the workflow. The workflow run can be found here: https://github.com/gau-nernst/kornia-rs/actions/runs/4277566348

@ducha-aiki To test the wheels, you can go to my workflow run, scroll to the bottom, and find the wheels artifact. I think you should be able to download the wheels from my branch. I don't see any permission control settings regarding the artifacts.

[edgarriba]

@gau-nernst any idea why linux failed in your branch ?

[gau-nernst]

@gau-nernst any idea why linux failed in your branch ?

I believe it is because I don't have permissions to the linux Docker images at ghcr.io/kornia

[ducha-aiki]

@gau-nernst I have checked the wheels from release, they work.

[edgarriba]

cool, i'll merge. @gau-nernst would be great to add a small new feature or something to make a new release and test the release workflow