-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Ament tools no longer in bin directory, and therefore not on path #199
Comments
Would you be willing to share the pixi activation script? I think it’ll make sense to “enforce” pixi for RoboStack with the rebuild we’re currently doing; any helper scripts etc would be very welcome! |
there might be more I’ve missed but this what I’ve encountered so far #!/bin/bash
export PATH=$PATH:$CONDA_PREFIX/lib/ament_lint_cmake/:$CONDA_PREFIX/lib/ament_xmllint/:$CONDA_PREFIX/lib/ament_cpplint/:$CONDA_PREFIX/lib/ament_copyright/ |
At a first glance the latest rebuild in #229 the packages are not affected by this problem, see:
However, to make sure we do not have regressions in this, I also added some smoke tests to check if the executables you mentioned in this issue can be correctly found in 1511e12 , so hopefully we should not have further regressions related to this. |
Solution to issue cannot be found in the documentation.
Issue
A number of the ament tools are no longer installed to the bin directory (since the py3.11 rebuild) and as a consequence are not on the path causing builds requiring them to fail. Adding them to the path solves the issue.
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: