Switch samples to use GLFW

[FacticiusVir]

Current sample projects use WinForms as the Surface host, which makes them dependent on Windows; GLFW is a cross-platform window library with explicit support for Vulkan Surfaces.

[FacticiusVir]

@sunkin351 Could you try the Test Harness project in the GLFW branch to see if it runs on Linux? I've tested on Win32 and it works okay for me. It'll need a 32-bit compile of libglfw.so which I don't have; you can change the project to an x64 build config and it should still work, or update the dllmap tag in App.config if you need to point to a different file.

[sunkin351]

I'm not sure what genius decided to name the vulkan library different on windows and linux, windows adds a "-1" to the end of the name before the file extension... which is irritating. Is there anything you can do about that at runtime?

Edit:
Also, since C# gives the feature of using [DllImport("vulkan")], I would advise using that instead of the complete library name and let the runtime choose.
I wonder if it will account for the "-1" in the windows name...

[FacticiusVir]

Mono supports DLL mapping - you can see an example here for my GLFW bindings: https://github.com/FacticiusVir/SharpVk/blob/Glfw/SharpVk/Test%20Harness/App.config
I'll add one to the repo, but in the meantime you can fix it directly in the build output by adding a SharpVk.dll.config file in the same format as the link, drop the startup element and update the dllmap line to be:
<dllmap os="linux" dll="vulkan-1.dll" target="vulkan.so"/>
(I'm assuming the Linux library is called vulkan.so)

[sunkin351]

libvulkan.so, but yea. I am changing a little code in the sample to match linux needs. (Xcb surface so far) Is it possible to compile once and have it run on multiple platform? (using dllmap and such?)

[sunkin351]

Btw, you wouldn't happen to know why vulkan is telling me I have two Graphics cards when I only have one, would you? (Nvidia GeForce GTX 750 Ti)

[FacticiusVir]

Is it the same name for both? If not, it might be picking up the on-chip GPU on some Intel CPUs.

[sunkin351]

Its the same name, type, and ID.
Plus my mb doesnt support onboard video.

[sunkin351]

Also, your sample has the same problem with CreateRenderPass().

[FacticiusVir]

Odd, not sure about the multiple physical devices; also, I'm reworking the marshalling/interop layer to fix the CreateRenderPass issue now, but it looks like a lot of the unmanaged memory code simply isn't Mono-compatible so it'll take me a little while.
For the XCB Surface change in the sample, is that just to include the correct extension name? If so, I can easily update the sample to detect the current platform's surface extension and load that, so it'll work cross-platform.

[sunkin351]

Its really funny, because that is the only function I have come across that creates a SigSegV. Everything else that isn't dependent on a render pass pretty much works from what I can tell. (Except for maybe all those warnings on device creation from the validation layers.)

[sunkin351]

I would hate to be a pest, but can you give me a timeframe to expect this done?

[FacticiusVir]

No worries, I've got some fixes in place that I'm testing, should have something to you this weekend.

[sunkin351]

Its the weekend. :)

[sunkin351]

Its the very end of the weekend, what do you have?