MacOS Monterey compilation issues #80
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I compiled ShaderConductor on MacOS Monterey version 12.4 and I found some issues in the process.
The CMakeList.txt file set c++ version as c++1z but I needed to set c++14 because DirectXShaderCompiler had errors with deprecated code in c++17 or high. I read in the official repo in the building source section that it required c++14.
On the other hand, in Source/Core/ShaderConductor.cpp the compiler throw an error in the line 293
std::atomic m_ref = 0;
I changed for this and the error disappeared
std::atomic m_ref = {0};