Vulkan-Hpp | Open-Source Vulkan C++ API | Build Tool library

This seems to work for me:

If we take a look at GLFW.h, it just includes vulkan.h only if the GLFW_INCLUDE_VULKAN macro is defined. So if you want to include the vulkan.hpp file, just undefine the GLFW_INCLUDE_VULKAN macro and include the file explicitly.

Why?
GLFW is a C library. vulkan.hpp file contains C++ stuff inside so there could be compatibility issues. That's why GLFW only includes vulkan.h and not vulkan.hpp.

There is no "Vulkan C++ specification". There's a header file containing some functions and types that make using Vulkan more C++-friendly. But those are not part of any actual specification.

The mapping from "VulkanHpp" into regular C Vulkan is pretty obvious in most cases and can be deduced just from the nature of the APIs in question. vk::ImageCreateInfo means the same thing, with the same fields, as VkImageCreateInfo as defined by the Vulkan specification. The C++ wrapper is not trying to confuse users as to how it works.

This is caused by the vulkan.hpp C++ header. It assumes that all functions are present, which is not the case for extension functions (that aren't part of the core). So you need to pass a dynamic dispatcher to the messenger callback creation function.

I'm not using vulkan.hpp myself, but it should look something like this in your case:

This template keyword is used to disambiguate the following expression as a template instantiation.

structureChain type depends on template parameters, so the compiler cannot know how to interpret the following get expression, which may be an instantiation of a get template, or comparison expression. The template keyword indicates that get is a template, and the following is a template instantiation. In the absence of this keyword the compiler would assume get is not a template, so the following must be a comparison expression.

See here.