-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GLFW cannot find vulkan/vulkan.h on macOS #35
Comments
M1 Chips don't support Vulkan. They only support Apple's own Metal API and OpenGL! |
btw MoltenVK exists but isn't official by Khronos or Apple Edit: MoltenVK is apperantly by the The Brenwill Workshop Ltd. and the Khronos Group, idk why I said it wasn't by the Khronos Group |
It sure feels like something you can install on your mac: https://vulkan.lunarg.com/doc/sdk/1.3.275.0/mac/release_notes.html
|
There are enough little oddities with mac that good cmakefiles should include an if (UNIX AND NOT APPLE) , and then provide the APPLE case if needed. Since the SDK will install in a weird place , you will need to tell it where to find the SDK ... let's say ~/VULKAN_SDK/version/here and then provide the necessary mods to the UNIX if statement to add_target_includes. |
@truedat101 idk if you were answering me, but MoltenVK (afaik) used to be smth that was unofficial not by the Khronos Group directly. I mentioned MoltenVK without saying you can't use it, and what you're talking about is exactly that. It's a layer for vulkan and not actually some type of support you can install for your hardware! Vulkan is a spec and Apple's M series chips do not support Vulkan directly, so they have to resort to translation like, the before mentioned, MoltenVK |
Vulkan does not link for me on macOS with
target_link_libraries(${PROJECT_NAME} glfw ${Vulkan_LIBRARIES})
CMakeLists.txt#L105.If I amend the
target_link_libraries
to includeVulkan::Vulkan
, it works fine.ccmake -GNinja ..
finds the Vulkan library okay:I'm on an M1 MacBook Pro, which I've found can have some slight oddities, but not sure why linking fails in this case.
¯_(ツ)_/¯
The text was updated successfully, but these errors were encountered: