Bear generates empty compile_commands.json when using VBCC frontend about bear HOT 3 CLOSED

Just after posting this I thought of putting the path to the actual vbccm68k executable as my CC environment variable instead of the vc frontend, and then it worked just fine and added the includes. Doh. So ignore this I guess. I do wonder if there is a way to not have to specify that every time? Shouldn't the /usr/lib/bear/wrapper.d/vbccm68k link handle that theoretically?

from bear.

@rsvensson I am happy that you could sort it out.

I can explain why it is a bit of trouble to use cross compilers... The two main things (that Bear does) are: intercept the executions and recognize them. When you put a link into the wrapper directory, that helps to intercept. To help recognize it, you need to create a config file and list the compiler in the compilation.compilers_to_recognize section.

When you specify the CC environment, that instruct Bear that this executable needs to be recognized.

On linux the interception works well without create a new wrapper executable. But still needs help to recognize the compiler calls.

from bear.

Thanks for your explanation!

Hmm but I did create a config file like that and tried to add both vc and vbccm68k to the compilers_to_recognize list. That did not help me in this case unfortunately, although it's possible I did something wrong. I don't have that config file saved anymore unfortunately. But it's not a big deal to specify the CC env var. I don't need to run Bear often enough to where it would be annoying.

Thanks for making this great piece of software btw!

from bear.