(C/C++) GoToDefinition cannot jump to source file in different directory

[ghqhxnfizloub]

For example, the project file tree is like this:

|- a
| |- a.c (where the definition of function a() is)
| \- a.h (where the declaration of function a() is)
|
|- b
| \- b.c (calls function a())
|
\- .ycm_extra_conf.py (directory 'a' is added into the flags)

If :GoToDefinition is called in b.c, an error about not being able to jump to definition is raised. If :GoToDefinitionElseDeclaration is called, Vim will jump to a.h but not a.c.

Thanks!

[Valloric]

From the YCM docs:

For C-family languages [GoToDefinition] only works in certain situations, namely when the definition of the symbol is in the current translation unit. A translation unit consists of the file you are editing and all the files you are including with #include directives (directly or indirectly) in that file.

[ghqhxnfizloub]

Not considering to add some project-scope code navigation feature? For example, add a funtion, say, GetSources(), in .ycm_extra_conf.py to get the list of source file names? Thanks!

[Valloric]

Maybe some time in the future, but not any time soon; it's difficult to implement well.

[ghqhxnfizloub]

Thanks for the reply. Maybe I will continue to use ctags and cscope to achieve that at the moment.

[sshsu]

Is it implemented? such feature is really playing a important role

[bstaletic]

No, but once clangd gets this ability, it will be in YCM.
For now you can jump to declaration and then open the corresponding source file and find the definition. Or you can get clever with your extra conf and automate that process.