Interaction between configurationProvider and other settings

[mmarczell-graphisoft]

Hello,

When I set

"configurationProvider": "ms-vscode.cmake-tools",
"forcedInclude": ["something.h"]

the forcedInclude setting is not respected. Is that a bug or intended behaviour? How can I overcome this?

The scenario is Emscripten development on a Mac, and currently there is no way to tell the development environment that it shouldn't display this error when including iostream:

cannot open source file "Availability.h" (dependency of "iostream")

I tried the approach suggested in #1083 (comment) but it didn't work.

[Colengms]

Hi @mmarczell-graphisoft . It's currently by-design that most other fields of the configuration are not used when using a custom configuration provider. One exception is the compilerPath field, which if set to a blank string can be used to disable use of the compiler provider by a custom configuration provider, which still using detected include paths, etc.. Otherwise, the other fields of the configuration are only used when the custom configuration provider does not provide a configuration for a file. It's expected that a custom configuration provider should provide a complete configuration for the file.

Since you are using CMake Tools, could you onfigure your CMakeLists.txt such that the forcedInclude is specified there, such as using a -include (gcc/clang) or /FI arg (cl.exe) ?

I'm not sure I understand the issue you are trying to work around. Is that error coming from the C/C++ Extension? Is "Availability.h" indeed a dependency of iostream? Is that file missing? Is the C/C++ extension failing to fully retrieve system include paths from the compiler?

[mmarczell-graphisoft]

Only the em++ compiler that I specified is ever mentioned in all of the logs. (For comparison, if I specify a nonexistent one, the logs tell me there was a fallback:

Specified compiler was not found: doesn'twork
Attempting to get defaults from compiler found on the machine: '/usr/bin/clang'

This does not happen with em++, it is found and queried.)

[sean-mcmanus]

Ok, can you confirm whether the em++ compiler defines __unix__ but not __linux__? If so, we could switch to checking for that.

[mmarczell-graphisoft]

That's correct

[sean-mcmanus]

Thanks for the info. I've created an issue at #7525 .

[sean-mcmanus]

Fixed with https://github.com/microsoft/vscode-cpptools/releases/tag/1.4.0-insiders2 -- i.e. let us know if you're still hitting an issue.