$HOME in Header Search Paths
Completed
How can I debug the way Header Search Paths are populated?
Somehow I've got my whole $HOME there so (re)indexing takes forever and "jump to definition" is all over the place, showing files with path stemming from $HOME instead of my local disk (I have a symlink $HOME/local pointing to the local disk, but the project is open from the local disk path directly, not thru the symlinked path).
Grepping .idea and .cache/JetBrains for the $HOME doesn't show anything obvious, almost everywhere I see the local disk paths, so I don't know what to fix for it to go away.
Any pointers?
Please sign in to leave a comment.
Hello!
Please open any problematic file (in which you do "jump to definition") and do
Help | Find Action>Show Compiler Info. What do you use in the Includes section there?Only local paths in the includes (`-I` and `-isystem` under `Compiler switches:`).
My $HOME is mentioned in one place only: `Pointer:` under `Header Search paths:` at the bottom. It looks like it just mirrors there what I see in the Project view
Could you please show the entire "Compiler switches" section of Show Compiler Info?
How can I do it securely? Let's create a ticket at YouTrack?
Ok, please create an issue in YouTrack, thanks.
What was the problem and how did you solve this issue?
I have the same issue currently and this makes Clion unusable for a couple of hours after startup.
Hi Tejas!
The problem was with the flag
-isystem/..which came from the 3rd party library.You can start investigating your case by checking the "Compiler switches" section of Show Compiler Info (
Help | Find Action>Show Compiler Info).I'm having the same issue too but I don't know how to fix it.
I looked into Show Compiler Info, and there's one offending line:
Pointer: file:///home/markNow I know the cause of the malfunctioning indexer, but how do I find out what causes this line to appear in the list of Header Search paths?
Mark Jeronimus, have you checked the “Compiler switches” section of Show Compiler Info (
Help | Find Action>Show Compiler Info)? Is there anything suspicious?Removing and reinstalling CLion from the JetBrains Toolbox seems to have fixed it.
Anna Falevskaya yes, I showed the suspicious line in the post above yours.
I checked the same file after re-installing CLion and the suspicious line is gone.
Since I only re-installed CLion and did nothing to the project, the project metadata was not at fault, neither the files in ~/.config/JetBrains