Closed d closed 3 years ago
Thanks @d for the report. Quick questions,
ccache
the result is good?ccache
away from the result? Or it could be scenarios when it is useful to have it?
- Do you expect that Bear always strips the
ccache
away from the result? Or it could be scenarios when it is useful to have it?
I do want to always strip it. My main uses of the compilation database are:
Thanks for the feedback. I'll try to make the change for the next release.
JetBrains supports open source projects by giving licenses to their tools. (I would not call it "sponsoring".) Neither I have been contacted from JetBrain to work on particular feature of Bear... But you can support the project if you like it via GitHub. ;)
Describe the bug I have a Makefile project (Postgres) where I've configured with
CC="ccache clang-11" CXX="ccache clang++-11"
and bear produces a compilation database that usesccache
as the command name. A snippet of such compilation database looks like the following:To Reproduce
cc.cc
with content:int main(){}
bear -- make CXX="ccache clang++-11" cc.o
cat compile_commands.json
Actual behavior
Expected behavior
Environment:
Context Such a compilation database is actually not usable in CLion as the command is not a compiler. Bear used to strip away the ccache wrapper, but we seem to have changed behavior here. Would you take patches? Where should I start?
Additional context