Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove use of @available() directive as it can cause issues in some build environments. #914

Merged
merged 4 commits into from
Jun 11, 2020

Conversation

billhollings
Copy link
Contributor

@billhollings billhollings commented Jun 11, 2020

  • Remove use of @available() directive as it can cause issues in some build environments.
  • Refactor Xcode build architectures.
  • Demo API-Samples generateSPIRVShaders no longer builds MoltenVKShaderConveter tool.

Fixes issue #913.

Set ARCHS build setting to $(ARCHS_STANDARD_64_BIT) in Xcode projects.
Remove ARCHS and VALID_ARCHS build settings in Xcode targets.
…Controller tool.

The tool will be built during MoltenVK build, and rebuilding just the tool
was clearing away the main MoltenVK build.
…uild environments.

Generally replace use of @available() with respondsToSelector:.
Add mvkMakeOSVersion() and mvkOSVersionIsAtLeast(macos,ios) to help testing OS versions.
Set maxDrawIndexedIndexValue to kMVKUndefinedLargeUInt32 instead of uint32_t max.
@@ -1476,7 +1476,7 @@
_properties.limits.maxComputeWorkGroupCount[1] = kMVKUndefinedLargeUInt32;
_properties.limits.maxComputeWorkGroupCount[2] = kMVKUndefinedLargeUInt32;

_properties.limits.maxDrawIndexedIndexValue = numeric_limits<uint32_t>::max();
_properties.limits.maxDrawIndexedIndexValue = kMVKUndefinedLargeUInt32;
Copy link
Collaborator

@cdavis5e cdavis5e Jun 11, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why? If the fullDrawIndexUint32 feature is supported, this is required to be the maximum uint32_t value. That's why I changed it to set it to numeric_limits<uint32_t>::max() in the first place. DXVK requires this for feature level 10 support, because all D3D10+ hardware supports it, and I'm pretty sure Metal (at least, on desktop) requires D3D11+ hardware.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shoot! My bad. I just interpreted it as a typo...without fully absorbing how that limit is special.

Fixing it now...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching that! 🤦🏻‍♂️😏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants