Community
Participate
Working Groups
When the user tries to follow an include file via the UI, OpenIncludeAction gathers a list of candidates and if there's only one, opens it automatically. In our project the build process fills a "dist/include" directory with symlinks to a number of include files in the project proper and that directory is added as a -I parameter. It is quite common for the same file to end up accessible both via normal include path searching and dist/include. This stops Eclipse from automatically navigating to the file.
Created attachment 24314 [details] fix This patch fixes the issue. When we find a candidate include file in the include paths, if it's not in the workspace but it's a symlink to a file that is in the workspace, we use the workspace file instead. We also throw out duplicate files. As well as fixing the automatic following behaviour, it also means that if a symlink to a project include file is found in the include paths, we will open the project include file, not the symlink. This is quite helpful.
(In reply to comment #1) > > This patch fixes the issue. When we find a candidate include file in the > include paths, if it's not in the workspace but it's a symlink to a file that > is in the workspace, we use the workspace file instead. We also throw out > duplicate files. > > This is quite helpful. Yes, it sounds that it could be.
Patch in the head. Please take time to verify this. Thanks
