Installation on Mac OS fails due to libvulkan not being code signed

[SirVer]

Following the installation instructions in the README, everything installs and builds correctly, but running the binary opens a warning window from Mac OS

Canceling this opens three other windows for other Vulkan libraries. The program does not start.

Is that a known issue? I could not find an explanation on how to correctly install Vulkan on Mac with code signed binaries.

Os: Mac OS Catalina 10.15.2

[Kethku]

The readme suggests brew cask install apenngrace/vulkan/vulkan-sdk but I don't have a mac so I'm not sure.

[SirVer]

Yes, that is what I did, but this led to the problems I described above. I hope somebody more Mac savvy will come by this issue and give some clue to what the solution might be.

[terhechte]

You can allow this in settings:

Basically:

• Try to run it
• Go to that settings screen
• Allow
• Try to run it again, a different library will pop up with an issue
• Allow again
• repeat
• You should also get dialogs with the "Open" option. Hit open in there.
• After like three runs it should run

[SirVer]

@terhechte Thanks, that did work. @Kethku, it is probably worthwhile to link this comment in the README for mac os x.

[bigOconstant]

You can allow this in settings:

Basically:

* Try to run it

* Go to that settings screen

* Allow

* Try to run it again, a different library will pop up with an issue

* Allow again

* repeat

* You should also get dialogs with the "Open" option. Hit open in there.

* After like three runs it should run

I'm able to do this when running cargo run, but not when trying to click on the executable from a release build. That just crashes for me atm.

[baileyn]

It worked for me on Mac OS Mojave 10.14.6 using the vulkan sdk installer from lunarg. I know it's not ideal, but it seems to work.

[terhechte]

I'm able to do this when running cargo run, but not when trying to click on the executable from a release build. That just crashes for me atm.

I can't test this right now, but could you try right-clicking the executable and then saying "open"?

[bigOconstant]

I'm able to do this when running cargo run, but not when trying to click on the executable from a release build. That just crashes for me atm.

I can't test this right now, but could you try right-clicking the executable and then saying "open"?

Yeah same thing. I installed the Vulkin sdk with brew cask install apenngrace/vulkan/vulkan-sdk

[Kethku]

@terhechte adding it to the readme. I will watch this issue for future developments. Thanks so much for the investigation!

[Kethku]

There is some talk about way we can switch to a library agnostic system which should remove the vulkan dependency for macos. May take a bit though

[SirJson]

That would be? OpenGL? That is even more broken on macOS from what I have heard, Apple wants to push the Metal API.

And OpenGL is hit and miss on Windows + very dependent on the driver that is running on that system. There is a reason why all major Browser Developer bundle ANGLE for WebGL Support on Windows.

[Kethku]

We're looking at wgpu

[Kethku]

Which has targets for directx, vulkan, and metal. Its still preliminary. Conversation is happening here: https://gitter.im/neovide/community

[tssm]

If you want to keep using Vulkan there's MoltenVK for macOS, which is an implementation of the Vulcan API on top of Metal

[Kethku]

Very interesting. Is it a drop in replacement? When installed does it run normally or do I have to add explicit support to my app somehow?

[Kethku]

Ah its a for pay product. That kinda disqualifies it

[tssm]

It's license is Apache 2.0. But it is not a drop-in replacement though.

I'll try what @baileyn did on my machine. Maybe Neovide could be statically linked against Vulkan, at least for macOS.

[Kethku]

This is well outside my area of knowledge. If someone wanted to attempt something like that is greatly appreciate it

_{Sent with GitHawk}

[tssm]

I'm trying to do it, but I haven't been successful. @baileyn could you describe what you did, please? I would like to try that on my machine

[baileyn]

I'm sorry. All I did was download the latest SDK for Mac from lunarg. After that, I just compiled again with cargo build --release.

It's possible our issues were slightly different?

[Kethku]

I just pushed an opengl backend to the main branch. Would folks struggling with this issue be willing to try it?

[tssm]

Does anyone have an idea of why I may be getting this error?

note: Undefined symbols for architecture x86_64:
        "____chkstk_darwin", referenced from:
            SkBlurMaskFilterImpl::filterRRectToNine(SkRRect const&, SkMatrix const&, SkIRect const&, SkMaskFilterBase::NinePatch*) const in libskia_bindings-f53e790636e34b91.rlib(libskia.SkBlurMF.o)
            SkBlurMaskFilterImpl::filterRectsToNine(SkRect const*, int, SkMatrix const&, SkIRect const&, SkMaskFilterBase::NinePatch*) const in libskia_bindings-f53e790636e34b91.rlib(libskia.SkBlurMF.o)
            SkCopyStreamToData(SkStream*) in libskia_bindings-f53e790636e34b91.rlib(libskia.SkStream.o)
            SkShaderMF::filterMask(SkMask*, SkMask const&, SkMatrix const&, SkIPoint*) const in libskia_bindings-f53e790636e34b91.rlib(libskia.SkShaderMaskFilter.o)
            SkPerlinNoiseShaderImpl::PaintingData::init(float) in libskia_bindings-f53e790636e34b91.rlib(libskia.SkPerlinNoiseShader.o)
            SkPicture::backport() const in libskia_bindings-f53e790636e34b91.rlib(libskia.SkPicture.o)
            OpDebug(SkPath const&, SkPath const&, SkPathOp, SkPath*) in libskia_bindings-f53e790636e34b91.rlib(libskia.SkPathOpsOp.o)
            ...
      ld: symbol(s) not found for architecture x86_64
      clang-7: error: linker command failed with exit code 1 (use -v to see invocation)

[Kethku]

That is a very strange error. Is it possible a debugger is trying to attach? I'm guessing thats hiding the actual error...

[poetaman]

@Kethku "I just pushed an opengl backend to the main branch. Would folks struggling with this issue be willing to try it?" Does that mean we don't need Vulkan anymore? (I have had issues installing it on my system)

[Kethku]

@reportaman yes. Unfortunately there were some issues. This code is now held in the opengl branch.

[Kethku]

I think this has been fixed in main. Please reopen if you come back to this and the issue remains.