Annoying dynamic_reconfigure code regeneration on catkin_make

edit

The dynamic reconfigure code generation looks it is being executed unconditionally even if the python generation script (.cfg) did not change.

This means that everytime that catkin_make command is called some new header (.h) files are generated by the dynamic_reconfigure cmake functionality. Because of this, the "incremental build mechanism" of cmake gets broken and your *.cpp files that depens on those headers recompile. This may make the development process slower.

Is this the expected behavior of the dynamic_reconfigure code generation system? Is there any way to avoid breaking the incremental build of cmake?

Until the current moment I have worked with these approaches (but I would like to avoid them because they do not satisfy me totally):

• the dynamic reconfigure files to other project and use the catkin_make's "black package list"
• building manually the targets I need the catkin_make's "--pkg" flag