-
Hello, I use With v2 of bear, I used the following line: Since v3, I must provide the verbatim path to "compilers_to_recognize": [
{
"executable": "/home/michel/.arduino15/packages/arduino/tools/arm-none-eabi-gcc/4.8.3-2014q1/bin/../lib/gcc/arm-none-eabi/4.8.3/cc1plus"
}
], Any idea on how this could be improved? Thanks a lot |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hey @m-dhooge , good question. Yes, in v3 most of the command line flags went to the configuration file. The drive behind is, that adding new functionalities to the tool would have created so many flags. And some of those functionalities would require multiple configuration which are belongs together, which is hard to represent with flags. The flag One simplification could be, the Bear picks up the |
Beta Was this translation helpful? Give feedback.
Hey @m-dhooge , good question.
Yes, in v3 most of the command line flags went to the configuration file. The drive behind is, that adding new functionalities to the tool would have created so many flags. And some of those functionalities would require multiple configuration which are belongs together, which is hard to represent with flags. The flag
--use-cc
and--use-c++
might arguable simple enough to keep it in the flags, but keep things simple I did move those to the config.One simplification could be, the Bear picks up the
CC
andCXX
variables and threat them as compiler names which has to be recognized, even if those are not in the config file. But I'm not sure if thecc1plus
is a c…