Why can't `arduino.json` "output" share the same output folder that is generated for debugging?

[zfields]

I LOVE the debugging feature of VSCode for Arduino!

When I debug, instead of using a /tmp folder, it automatically creates the folder ${workspaceRoot}/.build/BluesW - I love it.

What I don't love, is that I can't use that same folder for the output key in my arduino.json. If I specify .build/BluesW to match the folder that has already been created, then it will put the binaries in .build/BluesW/BluesW. However, when I simply specify .build it will place the binaries in the root of the .build folder (as you would expect). 🤷

Also, if I completely remove the .build folder, but I have a nested path (e.g. .build/BluesW) specified for output, then it throws an error that the directory does not exist.

Please check the "output" in the sketch Settings.Cannot find the output path:/home/zak/Development/Arduino/gh-issue-1473/.build/BluesW

Here is my arduino.json file:

arduino.json
{
"configuration": "pnum=SWAN_R5,upload_method=swdMethod,xserial=generic,usb=CDCgen,xusb=FS,opt=ogstd,dbg=enable,rtlib=nano",
"board": "STMicroelectronics:stm32:BluesW",
"port": "/dev/ttyACM0",
"sketch": "gh-issue-1473.ino",
"output":".build/BluesW/"
}

[gcampbell-msft]

@zfields Could you share your test project including your debug configuration (launch.json if you have one) so that I can attempt to repro? Thanks!

[zfields]

What board do you have? I'll try and tailor a project just for you.

IIRC, you can just use the extension to create the blink sketch, and try and debug it and it will cause the issue to repro when it generates the build. No board required.

[gcampbell-msft]

I'm using one of the STM Discovery Boards, STMicroelectronics B-L4S5I-IOTOA1.

My main question is what your debugging configuration looks like.

[zfields]

For the most part, it's the one that gets generated by the extension. I'm using OpenOCD as well.

Here are the full instructions.
https://dev.blues.io/quickstart/swan-quickstart/#debugging-arduino-with-vs-code

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Arduino",
            "type": "arduino",
            "request": "launch",
            "program": "${file}",
            "cwd": "${workspaceFolder}",
            "MIMode": "gdb",
            "targetArchitecture": "arm",
            "miDebuggerPath": "",
            "debugServerPath": "/usr/bin/openocd",
            "debugServerArgs": "-f interface/stlink.cfg -f target/stm32l4x.cfg",
            "customLaunchSetupCommands": [
                {
                    "text": "target remote localhost:3333"
                },
                {
                    "text": "file \"${file}\""
                },
                {
                    "text": "load"
                },
                {
                    "text": "monitor reset halt"
                },
                {
                    "text": "monitor reset init"
                }
            ],
            "stopAtEntry": true,
            "serverStarted": "Info\\ :\\ [\\w\\d\\.]*:\\ hardware",
            "launchCompleteCommand": "exec-continue",
            "filterStderr": true,
            "args": []
        }
    ]
}

[gcampbell-msft]

Great. I'll attempt to repro as soon as my bandwidth allows and try to make sure this is reproducible.

I should also mention that the experience you're describing is very likely by design (I'll look into this along with attempting to reproduce), as build files often get overwritten and its often better practice to keep them separate.

[zfields]

Kinda, sorta... I don't think it should arbitrarily choose a directory, it should probably throw an error and/or warning.

I would prefer to be able to specify this decision in a parameter instead of it being decided for me.

[gcampbell-msft]

@zfields What version of the extension do you have installed? I'm able to repro the first scenario you mentioned .build/BluesW/BluesW, but not the second where it lets you specify simply .build.