NB: I'm not using the full SDK, only the devicetree extension.
therefore I must provide the path to zephyr base.
app.code-workspace
{
"settings":
{
"devicetree.zephyr": "C:/Development/projects/firmware/zephyr/"
}
}
This works:
Unfortunately, this is not ideal for a shared project, so instead:
{
"settings":
{
"devicetree.zephyr": "${workspaceFolder}/../zephyr/"
}
}
and immediately, the extension is unhappy:
I have tried many variations, including using settings.json instead of workspace, but the behaviour remains the same.
The problem is that every clone of a project that uses this extension would need to change this path, and should be cautious about staging that change in a future commit.
if the user had a T1 workspace for all projects then they could just put the full path in their users settings.json file, but this won't help with a T2 project where the zephyr path is project specific.
This makes me certain that this is a bug/oversight. I think it used to work in a previous release but I am not 100% sure on that.
kind regards,
Andy
