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

ctrl clicking functions sometimes opens includes from install space #283

Open
koenlek opened this issue Jun 25, 2018 · 2 comments
Open

ctrl clicking functions sometimes opens includes from install space #283

koenlek opened this issue Jun 25, 2018 · 2 comments
Labels

Comments

@koenlek
Copy link

koenlek commented Jun 25, 2018

We use catkin tools with install space enabled (catkin config --install).

If we have a CMakeLists.txt that installs the include directory, e.g.

install(DIRECTORY
    include/
  DESTINATION ${CATKIN_GLOBAL_INCLUDE_DESTINATION}
)

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.

@Levi-Armstrong
Copy link
Member

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.

@koenlek
Copy link
Author

koenlek commented Oct 5, 2018

Any chance that this will be looked at by someone? It still causes confusion and loss of work (when accidentally working in an installed file) for us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants