Skip to content
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

Use conda-forge pinning when buildind conda packages #708

Closed
traversaro opened this issue May 4, 2021 · 2 comments
Closed

Use conda-forge pinning when buildind conda packages #708

traversaro opened this issue May 4, 2021 · 2 comments

Comments

@traversaro
Copy link
Member

traversaro commented May 4, 2021

In https://github.com/robotology/robotology-superbuild/actions/runs/808472915, we experienced a failure because blocktest is being built with the recently released Boost 1.76 (conda-forge/boost-feedstock#115, robotology/blocktest#47).

This highlighted that to avoid differences in the version installed in our binaries vs the binaries compiled via conda-forge, we need to build our packages by considering on the top of our local conda_build_config.yml (see https://github.com/robotology/robotology-superbuild/blob/master/conda/conda_build_config.yml) the conda_build_config.yml of conda-forge contained in https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/master/recipe/conda_build_config.yaml, that contains the specific pinned version of dependencies used in conda-forge . In this case, using that files would have built blocktest with Boost 1.74, as it happens on conda-forge source build, where bullet is installed also as a dependency of Gazebo, and so with version 1.74 .

@traversaro
Copy link
Member Author

This will help for #641 .

@traversaro
Copy link
Member Author

Fixed in #710 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant