Closed MichaelVoelkel closed 7 months ago
Oh damn. compile-commands-dir
wants drumrolls a directory and not the filepath. This already solves it. No clue why Intellisense still worked, I thought I had disabled it for the normal c/cpp extension via "C_Cpp.intelliSenseEngine": "disabled",
.
Anyways! Sorry for waste of time in case anyone read it already.
Being on macOS with Apple Silicon here. (Sonoma)
So I tried using VSC clangd but it cannot find symlinks.
In settings.json I have:
The compile_commands file is recognized because all my internal symbols work nicely.
Maybe an excerpt from my compile_commands.json file:
If I follow through myself, I see that:
is a symlink to
while
Versions/Current
is a symlink to A. So in essence (and this works with the "normal" VSC c/c++ intellisense) the whole think goes to:And there I find a file like
QAbstractItemModel
. However, clangd tells me, it cannot find it.Verbose logs are enabled, the relevant part is probably this (at least searching for QAbstractItemModel does not reveal anything better):
My unqualified assumption is that clangd has problems with this "symlink-complicated" Qt include structure. No clue why but it's definitely annoying. Any idea?
It can probably be rather macos-clangd-related. Then again, I think QtCreator also uses
clangd
but clearly works. So I'm a bit puzzled now.