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

ParsePath does not work for generated files in a devel workspace #722

Open
wxmerkt opened this issue Aug 13, 2020 · 2 comments
Open

ParsePath does not work for generated files in a devel workspace #722

wxmerkt opened this issue Aug 13, 2020 · 2 comments

Comments

@wxmerkt
Copy link
Collaborator

wxmerkt commented Aug 13, 2020

When a file is generated in a devel workspace, the path resolution is not clear: generated files live in devel/share/{package_name}; while rospack will resolve to src/{package_name}. Perhaps we need to get all possible paths and check them?

This can happen with URDF files that are generated during build from xacro.

@VladimirIvan
Copy link
Collaborator

The generated URDF files get copied into the SRC where ParsePath should pick it up correctly. Am I missing something here? Or was this a recent change to how xacro functions and it got resolved?

@wxmerkt
Copy link
Collaborator Author

wxmerkt commented Nov 5, 2020

Not every function call to xacro generates them in src/ because technically you are not supposed to modify the source directory. The overlay will search both devel and src. Our ParsePath currently does not do that.

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

2 participants