Ryujinx/moltenvk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixes to documentation for extensions and building.

Browse Source 
Indicate both vk_KHR_maintenance1 & vk_AMD_negative_viewport_height extensions are available.
This commit is contained in:
Bill Hollings 2018-09-16 14:46:01 -04:00
parent e546b83852
commit 5d8d4d2440
5 changed files with 22 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Docs/MoltenVK_Runtime_UserGuide.md
View File

@ -237,11 +237,16 @@ in your source code files as follows:
In addition to the core *Vulkan* API, **MoltenVK** also supports the following *Vulkan* extensions: In addition to the core *Vulkan* API, **MoltenVK** also supports the following *Vulkan* extensions:
- `VK_MVK_moltenvk` - `VK_MVK_moltenvk`
- `VK_KHR_swapchain`
- `VK_KHR_surface`
- `VK_MVK_ios_surface` (iOS)
- `VK_MVK_macos_surface` (macOS) - `VK_MVK_macos_surface` (macOS)
- `VK_AMD_negative_viewport_height` - `VK_MVK_ios_surface` (iOS)
- `VK_KHR_surface`
- `VK_KHR_swapchain`
- `vk_KHR_maintenance1`
- `vk_AMD_negative_viewport_height`
- `vk_KHR_shader_draw_parameters`
- `vk_KHR_get_physical_device_properties2`
- `vk_KHR_push_descriptor`
- `vk_KHR_descriptor_update_template`
- `VK_IMG_format_pvrtc` (iOS) - `VK_IMG_format_pvrtc` (iOS)
In order to visibly display your content on *iOS* or *macOS*, you must enable the `VK_MVK_ios_surface` In order to visibly display your content on *iOS* or *macOS*, you must enable the `VK_MVK_ios_surface`

1
MoltenVK/MoltenVK/GPUObjects/MVKDevice.mm
View File

@ -1551,7 +1551,6 @@ MVKDevice::MVKDevice(MVKPhysicalDevice* physicalDevice, const VkDeviceCreateInfo
_commandResourceFactory = new MVKCommandResourceFactory(this); _commandResourceFactory = new MVKCommandResourceFactory(this);
// Verify the requested extension names. Should be same as those requested from instance.
MVKExtensionList* pWritableExtns = (MVKExtensionList*)&_enabledExtensions; MVKExtensionList* pWritableExtns = (MVKExtensionList*)&_enabledExtensions;
setConfigurationResult(pWritableExtns->enable(pCreateInfo->enabledExtensionCount, setConfigurationResult(pWritableExtns->enable(pCreateInfo->enabledExtensionCount,
pCreateInfo->ppEnabledExtensionNames, pCreateInfo->ppEnabledExtensionNames,

2
MoltenVK/MoltenVK/Layers/MVKExtensions.cpp
View File

@ -139,8 +139,6 @@ static bool mvkIsSupportedOnPlatform(VkExtensionProperties* pProperties) {
if (pProperties == &kVkExtProps_MVK_MACOS_SURFACE) { return false; } if (pProperties == &kVkExtProps_MVK_MACOS_SURFACE) { return false; }
#endif #endif
if (pProperties == &kVkExtProps_AMD_NEGATIVE_VIEWPORT_HEIGHT) { return false; }
return true; return true;
} }

2
MoltenVK/MoltenVK/Layers/MVKExtensions.h
View File

@ -44,8 +44,8 @@ struct MVKExtensionList {
MVKExtension vk_KHR_surface; MVKExtension vk_KHR_surface;
MVKExtension vk_KHR_swapchain; MVKExtension vk_KHR_swapchain;
MVKExtension vk_KHR_maintenance1; MVKExtension vk_KHR_maintenance1;
MVKExtension vk_IMG_format_pvrtc;
MVKExtension vk_AMD_negative_viewport_height; MVKExtension vk_AMD_negative_viewport_height;
MVKExtension vk_IMG_format_pvrtc;
MVKExtension vk_KHR_shader_draw_parameters; MVKExtension vk_KHR_shader_draw_parameters;
MVKExtension vk_KHR_get_physical_device_properties2; MVKExtension vk_KHR_get_physical_device_properties2;
MVKExtension vk_KHR_push_descriptor; MVKExtension vk_KHR_push_descriptor;

23
README.md
View File

@ -133,12 +133,16 @@ and package the entire **MoltenVK** runtime distribution package, or to build in
**MoltenVK** or **MoltenVKShaderConverter** components. **MoltenVK** or **MoltenVKShaderConverter** components.
To build a **MoltenVK** runtime distribution package, suitable for testing and integrating into an app, To build a **MoltenVK** runtime distribution package, suitable for testing and integrating into an app,
open `MoltenVKPackaging.xcodeproj` in *Xcode*, and use one of the following *Xcode Schemes*: open `MoltenVKPackaging.xcodeproj` in *Xcode*, and use one of the following *Xcode Schemes*, depending
on whether you want a *Debug* or *Release* configuration, and whether you want to build for both the
*iOS* and *macOS* platforms, or just one platform:
- **MoltenVK (Release)** - build the entire **MoltenVK** runtime distribution package using the - **MoltenVK Package (Debug)**
*Release* configuration. - **MoltenVK Package (Debug) (iOS only)**
- **MoltenVK (Debug)** - build the entire **MoltenVK** runtime distribution package using the - **MoltenVK Package (Debug) (macOS only)**
*Debug* configuration. - **MoltenVK Package (Release)**
- **MoltenVK Package (Release) (iOS only)**
- **MoltenVK Package (Release) (macOS only)**
Each of these`MoltenVKPackaging.xcodeproj` *Xcode* project *Schemes* puts the resulting packages in the Each of these`MoltenVKPackaging.xcodeproj` *Xcode* project *Schemes* puts the resulting packages in the
`Package` directory, creating it if necessary. This directory contains separate `Release` and `Debug` `Package` directory, creating it if necessary. This directory contains separate `Release` and `Debug`
@ -156,13 +160,10 @@ app with either a **Debug** build, or a higher-performance **Release** build.
### Building from the Command Line ### Building from the Command Line
If you prefer to build **MoltenVK** from the command line, or to include the activity in a larger build script, If you prefer to build **MoltenVK** from the command line, or to include the activity in a larger build script,
you can do so using the following command from within the `MoltenVK` repository: you can do so using the following command within the `MoltenVK` repository, and identifying one of the
*Xcode Schemes* from the list above:
xcodebuild -project MoltenVKPackaging.xcodeproj -scheme "MoltenVK (Release)" build xcodebuild -project MoltenVKPackaging.xcodeproj -scheme "MoltenVK Package (Release)" build
or
xcodebuild -project MoltenVKPackaging.xcodeproj -scheme "MoltenVK (Debug)" build