Replies: 2 comments 6 replies
-
Can you use a multi-root workspace, with one folder per directory that has a different configuration? The configurationProvider property is meant to be used with a configuration provider extension, such as CMake Tools or Makefile Tools. |
Beta Was this translation helpful? Give feedback.
-
Hi, On my side I use a lot of workspaces for a lot of different projects, and each of them can have a lot of mixed content (many languages used, projects like PoCs, applications, tools, libraries, etc.). So eventually they are all multi-root (lots of roots), but I edit those roots very often based on what I want to focus on at a specific time. My point is: having the specific configuration be based on a workspace folder is not viable for me, and I wish it could be per file system folder, independently of the workspace organization. That would also mean that the conf could provide a variable similar to To illustrate my example:
Unless I missed something, this is not achievable unless I do add Is there a hard limitation from VSCode regarding the config file being bound to a workspace folder? |
Beta Was this translation helpful? Give feedback.
-
The project I'm working on comprises modules build with a variety of C/C+ compiler toolchains, but the c_cpp_properties.json file only allow me to activate a single configuration at a time. Is there a way to assign different configurations to different directories and have them work in parallel? Currently when I swap from one toolchain to another I get masses of warnings for directory trees that are not built with the new toolchain.
I've come across the
configurationProvider
property but there' s no information on how to use it.Beta Was this translation helpful? Give feedback.
All reactions