-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Build against both ogre 1.12 and 1.10 #85
Conversation
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 ( |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2021.07.19.17.59.15
@conda-forge-admin, please rerender |
…nda-forge-pinning 2021.07.19.17.59.15
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2021.07.19.17.59.15
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. |
I suspect all the failure are unrelated to the actual PR and related to conda-forge/qwt-feedstock#28 . Let's try with a clean build. |
The |
This will probably be necessary in any case to install gazebo in a ros2 environement with rviz2 installed. However, my main interest right now is to debug the ogre 1.12 build of conda-forge (for RoboStack/ros-galactic#24), as I already had experience in using Gazebo with Ogre 1.12 built via vcpkg, so it is more familiar for me to debug any problem here.
I tried to use
track_features
to de-prioritize ogre 1.12, but I am not sure if this actually works, but I gave it a shot.Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)