Fix build on arm64 #3
Merged
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
Signed-off-by: Addisu Z. Taddese <addisu@openrobotics.org>
Signed-off-by: Addisu Z. Taddese <addisu@openrobotics.org>
Signed-off-by: Addisu Z. Taddese <addisu@openrobotics.org>
Signed-off-by: Addisu Z. Taddese <addisu@openrobotics.org>
j-rivero
reviewed
May 7, 2024
j-rivero
approved these changes
May 7, 2024
Co-authored-by: Jose Luis Rivero <jrivero@osrfoundation.org>
azeey
added a commit
that referenced
this pull request
May 7, 2024
Signed-off-by: Addisu Z. Taddese <addisu@openrobotics.org> Co-authored-by: Jose Luis Rivero <jrivero@osrfoundation.org>
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.
Ogre currently needs
SIMD_NEONSIMD_SSE2turned off in order to build on arm64 architecture. These are also used in our upstream Ogre-next packages:I've tested this locally with docker (with qemu) and it built successfully.
Upstream issue: OGRECave/ogre-next#430