You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This can confuse QtCreator, because now some includes are available in the catkin_ws/src and in the catkin_ws/install folder (after a catkin build). This can be very annoying in practice, because sometimes you ctrl click in QtCreator into a header and make some edits there. After the next catkin build, these edits will be overwritten again with the header from below the src space. All that work will be wasted. This happened a couple of times already to me today.
It would be great if we can get the QtCreator ROS Plugin to tell QtCreator to prefer the includes in src over the ones in install. Maybe a similar fix as the one in #30 will do.
If desired I can provide a minimal example that (stochastically but surely) reproduces this issue.
The text was updated successfully, but these errors were encountered:
Yea when building the code model it does not order the includes generated from the CMake Code Block generator is not in the same order as the PATH Environment Variable. It should not be to difficult to add a sorter that sorts the include directory using the PATH Environment Variable so follow under cursor works.
We use catkin tools with install space enabled (
catkin config --install
).If we have a CMakeLists.txt that installs the include directory, e.g.
This can confuse QtCreator, because now some includes are available in the
catkin_ws/src
and in thecatkin_ws/install
folder (after acatkin build
). This can be very annoying in practice, because sometimes you ctrl click in QtCreator into a header and make some edits there. After the nextcatkin build
, these edits will be overwritten again with the header from below thesrc
space. All that work will be wasted. This happened a couple of times already to me today.It would be great if we can get the QtCreator ROS Plugin to tell QtCreator to prefer the includes in src over the ones in install. Maybe a similar fix as the one in #30 will do.
If desired I can provide a minimal example that (stochastically but surely) reproduces this issue.
The text was updated successfully, but these errors were encountered: