Missing conda dependency spdlog
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- build-system
Research direction
Start with the pixi environment dependency declaration in the issue and investigate how WalkingControllers 0.9 declares or packages its spdlog dependency. Reproduce the missing-library error with the shown environment, then confirm that WalkingModule runs without a manual spdlog version pin while remaining compatible with the other dependencies.
Written by the indexing model from the issue text.
Description
Trying to run the WalkingModule from the followig pixi env:
[workspace]
authors = ["Giovanni Fregonese <[email protected]>"]
channels = ["conda-forge", "robotology"]
name = "gazebo_env"
platforms = ["linux-64"]
version = "0.1.0"
[tasks]
[dependencies]
yarp = ">=3.12"
whole-body-estimators = "*"
bipedal-locomotion-framework = "*"
ergocub-software = "*"
walking-controllers = ">=0.9"
gz-sim-yarp-plugins = "*"
results in:
pixi run WalkingModule
/home/giovannif/gazebo_env/.pixi/envs/default/bin/WalkingModule: error while loading shared libraries: libspdlog.so.1.15: cannot open shared object file: No such file or directory
Is spdlog a dependency of WalkingControllers?
Trying to pixi add spdlog results in an incompatible version since WalkingControllers 0.9 looks for libspdlog 1.15 but other dependecies require spdlog>=1.16, adding spdlog = ">=1.15.0, <1.16.0" works and the WalkingModule can run.
- Dominant language
- C++
- Stars
- 162
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from gbionics/walking-controllers
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
gbionics/walking-controllers#201 · 5 comments ·
-
setGoal not workingOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
gbionics/walking-controllers#195 · 5 comments ·
-
Prevent the joypad from connecting to the walking module automaticallyMay be free again @S-Dafarra claimed this 717 days ago, and no pull request is open. Open
gbionics/walking-controllers#192 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
gbionics/walking-controllers#163 · 18 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
gbionics/walking-controllers#142 · 3 comments ·
All issues in gbionics/walking-controllers
Similar issues
-
os:Linux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
acceptable_buffer_backends: unknown backend names are silently ignoredPossibly taken @mini-1235 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ros2/rmw_fastrtps#945 ·
Maintainers usually reply within 1 day
-
bot-triaged module: correctness (silent) module: mps module: NaNs and Infs triage review
Difficulty 2/5 Half a day Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day