Fix clang-specific compiler errors on Linux#292
Closed
jwindgassen wants to merge 1 commit intoTriAxis-Games:masterfrom
Closed
Fix clang-specific compiler errors on Linux#292jwindgassen wants to merge 1 commit intoTriAxis-Games:masterfrom
jwindgassen wants to merge 1 commit intoTriAxis-Games:masterfrom
Conversation
Contributor
Author
|
Duplicate of #293, use that instead |
This file contains hidden or 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
1 participant
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.
After upgrading to Unreal Engine 5.5, I experienced some problems when packaging my game for Linux using Cross-Compile.
Firstly
Error: '/*' within block comment [-Werror,-Wcomment], which only seems to appear with Clang since it has more warnings/errors enabled than MSVC.Secondly, I got
'MarkCollisionDirtyNoCallback' is a protected member of 'RealtimeMesh::FRealtimeMeshSimple', where I am unsure whether it's a compiler bug or not. I found other issues online that suggest this might be a clang bug. But whatever it is, the best solution I found was just making the function public instead of protected.