[Webkit-unassigned] [Bug 182689] Unified builds broke ycm autocompletion using compilation databases

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=182689

--- Comment #2 from Sergio Villar Senin <svillar at igalia.com> ---
(In reply to Keith Miller from comment #1)
> How did YCM work with headers in the past? 

YCM allows users to specify a control file where to add some more information or provide additional behaviours. There is one in Tools/gtk/ycm_extra_conf.py which is the one I was using. As you can see when asking for the compilation flags for a header file, the ones for the corresponding .cpp are returned instead

> Presumably, YCM just needs to be told that the actual source files are the
> unified-sources and everything else is a "header".

The problem is that YCM has a very specific interface. When you open a file in the editor (note that is never an unified file but the actual source) it asks for the compilation flags of that specific file (which is never found as the flags are used for the unified sources). The solution I foresee is one that allows ycm to map from source files to unified sources. Is that possible?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180213/78d1e038/attachment.html>