[cfe-dev] CompilationDatabase support added to libclang and python binding
klimek at google.com
Tue Jun 19 00:31:34 PDT 2012
On Tue, Jun 19, 2012 at 9:15 AM, Stephen Kelly <steveire at gmail.com> wrote:
> Manuel Klimek wrote:
> > On Tue, Jun 12, 2012 at 12:11 PM, Chandler Carruth
> > <chandlerc at google.com>wrote:
> >> On Tue, Jun 12, 2012 at 1:13 AM, David Röthlisberger
> >> <david at rothlis.net>wrote:
> >>> Could we please have some documentation on the format of the
> >>> compile_commands.json? (Manuel?).
> >> Just wanted to second this. I actually wanted to cite just such
> >> documentation in a new design proposal I'm about to mail out... =D
> > Committed as r158365.
> > http://clang.llvm.org/docs/JSONCompilationDatabase.html
> > Feeback or patches welcome :)
> > Cheers,
> > /Manuel
> The tooling doesn't seem to handle relative paths very well.
> If I have the directory /foo/bar and a build directory /foo/bar/build, and
> the compile_commands.json contains entries like "../blub.cpp", the tooling
> seems to not find the entry for blub.cpp.
> I fixed that for the Ninja generator in CMake here:
> but I think this might be a bug in clang (recall I brought up relative
> troubles yesterday too :)).
Awesome, thanks. Also, feel free to file bugs and assign them to me - it
might well be a problem in the tooling layer, I'm aware I haven't it tested
too well for the relative path edge cases...
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev