Add macOS GitHub Actions CI

[finn-fletcher]

Now that Windows GitHub Actions support has been added, we also need macOS CI to complete cross-platform coverage.

The goal is to provide a macOS job equivalent in functionality to the existing Linux and Windows manifest-based CI workflows.

[finn-fletcher]

Hi @chizkiyahu, thank you very much for adding the Windows CI support. Would you be interested at all in doing the macOS equivalent?

[chizkiyahu]

@finn-fletcher
I already started to work on this
The problem is in emulation layer tests
Without this is working

I tried very hard to install even from source a Vulcan ask that working without success

[chizkiyahu]

@davidegrohmann @finn-fletcher
I tried with SwiftShader and with Lavapipe
what is the best way to try ?

[davidegrohmann]

I would say lavapipe. Do you use MoltenVK as a compatible layer for Vulkan?

[chizkiyahu]

@davidegrohmann @finn-fletcher
is working

• Add macOS CI build configuration #103
• Update CMakeLists.txt for macOS library paths and JSON generation ai-ml-emulation-layer-for-vulkan#167
• Macos ci with tests #105 (needs 167)

[davidegrohmann]

@chizkiyahu Fantastic! Thanks! We are gonna review those patches asap.

[chizkiyahu]

@davidegrohmann

about the lines

sudo mkdir -p /usr/local/lib
sudo ln -s /opt/homebrew/lib/libvulkan.dylib /usr/local/lib/libvulkan.dylib

I open a PR KhronosGroup/Vulkan-Hpp#2383 to fix this

[chizkiyahu]

Vulkan-Hpp and Vulkan-Headers have released the fix in

• Vulkan-Hpp v1.4.337: https://github.com/KhronosGroup/Vulkan-Hpp/releases/tag/v1.4.337
• Vulkan-Headers v1.4.337: https://github.com/KhronosGroup/Vulkan-Headers/releases/tag/v1.4.337

With these releases, we should be able to remove the workaround in:

ai-ml-sdk-for-vulkan/.github/workflows/build-with-manifest.yml

Lines 111 to 112 in a94039c

	sudo mkdir -p /usr/local/lib
	sudo ln -s /opt/homebrew/lib/libvulkan.dylib /usr/local/lib/libvulkan.dylib

@davidegrohmann — what is the correct process for updating the version in ai-ml-sdk-manifest?

• Do we need to wait for a vulkan-sdk-1.4.x.y tag?
• Or is it acceptable for me to open a PR that updates the manifest to v1.4.337 directly?

[davidegrohmann]

@chizkiyahu I would stick using vulkan-sdk-1.4.x.y tags for now. We plan to move to vulkan-sdk-1.4.335. So we can keep the workaround in place until the next version of the vulkan-sdk is released with the fix.

We can close this issue and open a new one for removing the workaround so we do not forget.