ShuriZma
/
dolphin
mirror of https://github.com/dolphin-emu/dolphin.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
dolphin/Source/Core/VideoBackends/Vulkan/VulkanLoader.h

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

54 lines
1.4 KiB
C
Raw Normal View History

Implement experimental Vulkan backend
2016-08-13 12:57:50 +00:00
// Copyright 2016 Dolphin Emulator Project
// Licensed under GPLv2+
// Refer to the license.txt file included.
#pragma once
#define VK_NO_PROTOTYPES
#if defined(WIN32)
#define VK_USE_PLATFORM_WIN32_KHR
Vulkan: Support runtime selection of WSI
2018-10-24 04:47:48 +00:00
#endif
#if defined(HAVE_X11)
Implement experimental Vulkan backend
2016-08-13 12:57:50 +00:00
#define VK_USE_PLATFORM_XLIB_KHR
Vulkan: Support runtime selection of WSI
2018-10-24 04:47:48 +00:00
#endif
#if defined(ANDROID)
Implement experimental Vulkan backend
2016-08-13 12:57:50 +00:00
#define VK_USE_PLATFORM_ANDROID_KHR
Vulkan: Support runtime selection of WSI
2018-10-24 04:47:48 +00:00
#endif
#if defined(__APPLE__)
Vulkan: Switch from vkCreateMacOSSurfaceMVK() to vkCreateMetalSurfaceEXT() Since we are calling this off the UI thread, we can't use anything which accesses the underlying NSView object. We create and set the Metal layer on the UI thread before the video backend is initialized. This extension is both compatible with MoltenVK and gfx-portability for accepting a layer at surface creation.
2020-04-07 08:49:40 +00:00
#define VK_USE_PLATFORM_METAL_EXT
Implement experimental Vulkan backend
2016-08-13 12:57:50 +00:00
#endif
#include "vulkan/vulkan.h"
Vulkan: Exclusive fullscreen support via VK_EXT_full_screen_exclusive
2019-09-30 15:10:08 +00:00
// Currently, exclusive fullscreen is only supported on Windows.
#if defined(WIN32)
#define SUPPORTS_VULKAN_EXCLUSIVE_FULLSCREEN 1
#endif
Implement experimental Vulkan backend
2016-08-13 12:57:50 +00:00
// We abuse the preprocessor here to only need to specify function names once.
#define VULKAN_MODULE_ENTRY_POINT(name, required) extern PFN_##name name;
#define VULKAN_INSTANCE_ENTRY_POINT(name, required) extern PFN_##name name;
#define VULKAN_DEVICE_ENTRY_POINT(name, required) extern PFN_##name name;
#include "VideoBackends/Vulkan/VulkanEntryPoints.inl"
#undef VULKAN_DEVICE_ENTRY_POINT
#undef VULKAN_INSTANCE_ENTRY_POINT
#undef VULKAN_MODULE_ENTRY_POINT
namespace Vulkan
{
bool LoadVulkanLibrary();
bool LoadVulkanInstanceFunctions(VkInstance instance);
bool LoadVulkanDeviceFunctions(VkDevice device);
void UnloadVulkanLibrary();
const char* VkResultToString(VkResult res);
void LogVulkanResult(int level, const char* func_name, VkResult res, const char* msg, ...);
Use __func__ instead of __FUNCTION__ where applicable This replaces usages of the non-standard __FUNCTION__ macro with the standard mandated __func__ identifier. __FUNCTION__ is a preprocessor definition that is provided as an extension by compilers. This was the only convenient option to rely on pre-C++11. However, C++11 and greater mandate the predefined identifier __func__, which lets us accomplish the same thing. The difference between the two, however, is that __func__ isn't a preprocessor macro, it's an actual identifier that exists at function scope. The C++17 draft standard (N4659) at section [dcl.fct.def.general] paragraph 8 states: " The function-local predefined variable __func__ is defined as if a definition of the form static const char __func__[] = "function-name "; had been provided, where function-name is an implementation-defined string. It is unspecified whether such a variable has an address distinct from that of any other object in the program. " Thankfully, we don't do any macro or string concatenation with __FUNCTION__ that can't be modified to use __func__.
2018-03-16 17:27:11 +00:00
#define LOG_VULKAN_ERROR(res, ...) LogVulkanResult(2, __func__, res, __VA_ARGS__)
Implement experimental Vulkan backend
2016-08-13 12:57:50 +00:00
} // namespace Vulkan