You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bear currently doesn't resolve relative path components for the file key in each compilation entry. So if you invoke Bear with something like the following: bear -- sh -c "gcc /home/nick/foo/bar/../../fee.c", you get a compilation database entry like:
This is a problem, because when you feed a compilation database to libclang's CXCompilationDatabase, it doesn't canonicalise these paths for you. (At least not with LLVM 3.4.) If you ask it for the flags for /home/nick/fee.c, it won't return any results.
The text was updated successfully, but these errors were encountered:
Bear currently doesn't resolve relative path components for the
file
key in each compilation entry. So if you invoke Bear with something like the following:bear -- sh -c "gcc /home/nick/foo/bar/../../fee.c"
, you get a compilation database entry like:This is a problem, because when you feed a compilation database to libclang's CXCompilationDatabase, it doesn't canonicalise these paths for you. (At least not with LLVM 3.4.) If you ask it for the flags for
/home/nick/fee.c
, it won't return any results.The text was updated successfully, but these errors were encountered: