Hey,
it seems the extension ignores manually set include/browse paths once you have a compile_commands.json set up to be used. However in my case this file does not include the built-in toolchain include paths. Adding them to includePaths/browse does not seem to be recognized by the extension in this case.
Is the intentention for me to achieve this differently? Would it be possible to add these settings to the set gathered by parsing the compile_commands.json ?
Hey,
it seems the extension ignores manually set include/browse paths once you have a compile_commands.json set up to be used. However in my case this file does not include the built-in toolchain include paths. Adding them to includePaths/browse does not seem to be recognized by the extension in this case.
Is the intentention for me to achieve this differently? Would it be possible to add these settings to the set gathered by parsing the compile_commands.json ?