1.10arm migration

[Tobias-Fischer]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[Tobias-Fischer]

@conda-forge-admin, please rerender

[Tobias-Fischer]

Seems like this needs patching https://github.com/OGRECave/ogre/blob/v1.10.12/OgreMain/src/OgrePlatformInformation.cpp

[Tobias-Fischer]

Here's the relevant fix: OGRECave/ogre@0873244

[wolfv]

we could also go for Ogre 1.12 only for M1?

And only allow ignition gazebo? I think Traditional Gazebo was holding us back in general, right? (cc @traversaro)

[wolfv]

The screenshot I posted of RViz running on M1 was using 1.12 I think.

[traversaro]

And only allow ignition gazebo? I think Traditional Gazebo was holding us back in general, right? (cc @traversaro)

Actually also Classic Gazebo should work finish with Ogre 1.12, just a few rendering features are disabled (gazebosim/gazebo-classic#2686). There were some issues in the past (see gazebosim/gazebo-classic#2700), but hopefully they are not relevant anymore.

[Tobias-Fischer]

Hmmm, I think in this case we should try and get Gazebo11 working with Ogre 1.12 on the remaining platforms as well? In my opinion, we should avoid making exceptions as much as possible to avoid issues down the line.

[Tobias-Fischer]

I patched ogre 1.10 anyhow as it was easy enough, and if we want to, we can merge. I guess it doesn't hurt merging, even if we don't end up using it.