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
I just learn how to wirte clang libtooling. Bear project is very helpful for me. Thanks.
Now I have installed Bear and create the file compile_commands.json by compiling eglibc source code. But when I use libtooling to analyze file, there is still error "LLVM ERROR: Could not auto-detect compilation database for file, No compilation database found json-compilation-database: Error while opening JSON database: No such file or directory".
I get compile_commands.json in the /build. I use ln -s $PWD/compile_commands.json path/to/source/. It is still same error. I also copy compile_commands.json to current directory of the file which is prepared to analyze. Same error.
Can you give me some hits? What did I miss?
Thank you very much!
Sun
The text was updated successfully, but these errors were encountered:
hi Sun,
thanks for your message. sorry, i can't tell why your program does not work. Bear implements the compilation database, according to its definition. if it is not correct, please reopen this ticket and write your findings.
regards,
Laszlo
I just learn how to wirte clang libtooling. Bear project is very helpful for me. Thanks.
Now I have installed Bear and create the file compile_commands.json by compiling eglibc source code. But when I use libtooling to analyze file, there is still error "LLVM ERROR: Could not auto-detect compilation database for file, No compilation database found json-compilation-database: Error while opening JSON database: No such file or directory".
I get compile_commands.json in the /build. I use ln -s $PWD/compile_commands.json path/to/source/. It is still same error. I also copy compile_commands.json to current directory of the file which is prepared to analyze. Same error.
Can you give me some hits? What did I miss?
Thank you very much!
Sun
The text was updated successfully, but these errors were encountered: