-
Notifications
You must be signed in to change notification settings - Fork 156
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
Force config. regeneration when adding new params #58
Comments
One ugly option is to always touch the .cfg file, but this makes compilation longer when only it's occasionally needed:
|
You would need to add the file as a dependency to the add_custom_command in the generate_dynamic_reconfigure_options macro, i.e. here: |
Unfortunately not; generate_dynamic_reconfigure_options tries to process it as any other .cfg file |
> Maybe an extra parameter in for the macro works.
Unfortunately not; generate_dynamic_reconfigure_options tries to process it as any other .cfg file
I meant you can improve the generate_dynamic_reconfigure_options (i.e.
patch it), such that it supports your use case.
|
Change PRequested. @jspricke, maybe you can comment it, if it's not described clearly enough. |
When adding new params to https://github.com/magazino/move_base_flex/blob/master/mbf_abstract_nav/src/mbf_abstract_nav/__init__.py, you need to touch https://github.com/magazino/move_base_flex/blob/master/mbf_costmap_nav/cfg/MoveBaseFlex.cfg before compiling so code for the new parameters is generated.
Cannot do better?
The text was updated successfully, but these errors were encountered: