You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add support for specifying separate C and C++ compiler paths and args #9266
Currently, we have compilerPath and compilerArgs fields in c_cpp_properties.json. Arguments (i.e. -std=c++20 vs -std=c17), and perhaps even the compiler itself (i.e. XC16), can be C or C++ specific. These field may be insufficient for users who want to mix C and C++ sources. The same issue exists for fields in custom configuration provider interfaces.
This feature request tracks separating compilerPath and compilerArgs into C and C++, so separate values for each can be provided. One backwards compatible approach would be to allow the existing fields to be overloaded with an object containing a separate value per language. For example:
In some ways we are treating cuda-cpp as a separate language from C++, with it's own language ID. It might make sense for this feature to support cuda-cpp as well, and other language ID's that might be added in the future.
Activity
Colengms commentedon May 4, 2022
In some ways we are treating
cuda-cppas a separate language from C++, with it's own language ID. It might make sense for this feature to supportcuda-cppas well, and other language ID's that might be added in the future.