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

Moveit Packages in Iron: Ros-env cmake copy issue #391

Open
Thieso opened this issue Apr 14, 2024 · 2 comments · May be fixed by #397
Open

Moveit Packages in Iron: Ros-env cmake copy issue #391

Thieso opened this issue Apr 14, 2024 · 2 comments · May be fixed by #397

Comments

@Thieso
Copy link

Thieso commented Apr 14, 2024

Hello,

I am trying to install MoveIt in Ros2 Iron but for some package I get the error:

Running phase: fixupPhase
> moving /nix/store/rlzhp0g8haspl9w4a3dcp54zbhxpwgvq-ros-env/lib64/* to /nix/store/rlzhp0g8haspl9w4a3dcp54zbhxpwgvq-ros-env/lib
> mv: not replacing '/nix/store/rlzhp0g8haspl9w4a3dcp54zbhxpwgvq-ros-env/lib/cmake'

The packages that encounter this issue are:

  • moveit-ros
  • moveit-servo
  • moveit-planners

and possibly more which I have not tested.

Do you know what causes this error and how I may help to fix it?

Thank you

@Thieso
Copy link
Author

Thieso commented Apr 18, 2024

So after trying out a bit I figured that I used this

    devShells.x86_64-linux.default = pkgs.mkShell {
      name = "ros devenv";
      buildInputs = with pkgs; with pkgs.rosPackages.humble; [
        (buildEnv {
          paths = [
               moveit-servo
          ];
        })
      ];
   }

but it has to be

    devShells.x86_64-linux.default = pkgs.mkShell {
      name = "ros devenv";
      buildInputs = with pkgs; with pkgs.rosPackages.humble; [
               moveit-servo
      ];
   }

@Thieso Thieso closed this as completed Apr 18, 2024
@Thieso
Copy link
Author

Thieso commented Apr 21, 2024

Hi, so I think I should reopen this since the fix causes then problems with the python packages not being in the path such that this is not really a good fix. Is there a better way to fix it?

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

Successfully merging a pull request may close this issue.

1 participant