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

With pixi, tests link to pinocchio in .pixi/envs folder #2615

Open
abussy-aldebaran opened this issue Mar 11, 2025 · 3 comments
Open

With pixi, tests link to pinocchio in .pixi/envs folder #2615

abussy-aldebaran opened this issue Mar 11, 2025 · 3 comments
Assignees

Comments

@abussy-aldebaran
Copy link
Contributor

Bug description

When using pixi to build pinocchio, after a ninja install, tests link with pinocchio's libs that are installed in .pixi/envs/....

Expected behavior

When using pixi to build pinocchio, after a ninja install, tests link with pinocchio's libs that are in the build tree.

Reproduction steps

Steps to reproduce the behavior:

pixi run configure
pixi shell
cd build
ninja
ldd unittest/pinocchio-test-cpp-model | grep pinocchio_default
	libpinocchio_default.so.3.4.0 => /home/antoine.bussy/work/pinocchio/build/src/libpinocchio_default.so.3.4.0 (0x00007b8be4e00000)
ninja install
ldd unittest/pinocchio-test-cpp-model | grep pinocchio_default
	libpinocchio_default.so.3.4.0 => /home/antoine.bussy/work/pinocchio/.pixi/envs/default/lib/libpinocchio_default.so.3.4.0 (0x00007c5e9de00000)

Additional context

One possible cause is setting CMAKE_INSTALL_PREFIX=$CONDA_PREFIX in pixi.toml.

System

  • OS: ubuntu 24.04
  • Pinocchio version: devel (2f33ea1)
@abussy-aldebaran
Copy link
Contributor Author

I'm willing to submit a PR if you tell me if and how you wish to fix this.

@jcarpent
Copy link
Contributor

I do think @jorisv is the best to provide the proper guidance.
Thanks a lot, @abussy-aldebaran, for this issue and your willingness.

@abussy-aldebaran
Copy link
Contributor Author

You're welcome.
Here are some ideas :

  1. Set CMAKE_INSTALL_PREFIX to install, to mirror the build folder
  2. I wonder if installing makes sense in a pixi setup ? If no, the install target could be disabled with CMAKE_SKIP_INSTALL_RULES (https://cmake.org/cmake/help/latest/variable/CMAKE_SKIP_INSTALL_RULES.html)

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

3 participants