defines and includePath in c_cpp_properties.json

[mkitby]

Hi,

defines and includePath settings will be discarded if using compile_commands.json in c_cpp_properties.json. I think this is unreasonable. Both settings should be kept. Let's think about a cross compiler which is not supported by cpptools. In this case, the compilerPath setting will be defined as an empty string to skip querying a compiler. And compiler internal defines will NOT exist in compile_commands.json. We need to define it in defines setting.

[sean-mcmanus]

Cross compilation is supported in general...what issue are you hitting with that? We appear to be tracking your request with #6909 .

[mkitby]

same issue as #6909

[lakazatong]

I would like to add a follow up on that topic, compiling a project can be troublesome, whereas adding WIP header files in the includePath array is much easier and quicker.
Moreover as @mkitby said, it'"unreasonable" to discard include Path if a compile_commands.json is used, I'd even say it's unexpected behavior, I would expect both to complement each other, not one to override the other.
Imagine all of your includes working all of a sudden because you deleted your build directory... what a counter-intuitive side effect.