Ongy
> Many workspaces can exist on an output and each output has its own set of workspaces. This isn't exactly true in `waymonad` either. Workspaces are a "global" thing that...
You can check the Menu in File => Preferences Settings On the Settings editor: Extensions => Meson build configuration This lists the available settings (and lets you modify them). There...
Are you using meson subprojects to manage your projects, or do you have multiple toplevel projects in directories next to each other in your workspace?
Yes, the plugin currenlty only supports one project. We need to make a lot of internal code be less global to support more than one. The first step is likely...
Did you configure the project first? Either via the command inside vscode, or by calling meson directly?
That is, configured into the configured build directory. The error messages aren't too helpful when the directory doesn't exist, but it works for me when it does.
Since everything was switched to meson instead of using ninja in 318c1df82f7eedfc6456719e711276d95b1d7242 this shouldn't be an issue anymore. Can you please re-test. Maybe also @dresch86. I don't have a windows...
Looks like what was fixed in https://github.com/mesonbuild/vscode-meson/pull/80 but it's not yet in a release.
There's the `mesonbuild.buildFolder` setting for the extension. Is that not what you are looking for?
Do you still have this issue? I don't have a windows seutp, but works fine for me on linux with the current code.