Build Error: go build -o F:\....\debug_bin.exe -gcflags all=-N -l . no Go files in F:\....\ (exit status 1)

[John-zhan]

What version of Go, VS Code & VS Code Go extension are you using?

Version Information

• Run go version to get version of Go from the VS Code integrated terminal.
  • go.1.20.3
• Run gopls -v version to get version of Gopls from the VS Code integrated terminal.
  • No gopls
• Run code -v or code-insiders -v to get version of VS Code or VS Code Insiders.
  • 1.78.2
    b3e4e68a0bc097f0ae7907b217c1119af9e03435
    x64
    • No code-insiders
• Check your installed extensions to get the version of the VS Code Go extension
  • v0.38.0
• Run Ctrl+Shift+P (Cmd+Shift+P on Mac OS) > Go: Locate Configured Go Tools command.

Checking configured tools....
GOBIN: undefined
toolsGopath:
gopath: F:\personalFile\GoCode
GOROOT: D:\GoLang
go: D:\GoLang\bin\go.exe: go version go1.20.3 windows/amd64
gotests: F:\personalFile\GoCode\bin\gotests.exe (version: v1.6.0 built with go: go1.20.3)
gomodifytags: F:\personalFile\GoCode\bin\gomodifytags.exe (version: v1.16.0 built with go: go1.20.3)
impl: F:\personalFile\GoCode\bin\impl.exe (version: v1.1.0 built with go: go1.20.3)
goplay: F:\personalFile\GoCode\bin\goplay.exe (version: v1.0.0 built with go: go1.20.3)
dlv: F:\personalFile\GoCode\bin\dlv.exe (version: v1.20.2 built with go: go1.20.3)
staticcheck: F:\personalFile\GoCode\bin\staticcheck.exe (version: v0.4.3 built with go: go1.20.3)
gopls: F:\personalFile\GoCode\bin\gopls.exe (version: v0.11.0 built with go: go1.20.3)
go env
Workspace Folder (Xray-core): f:\personalFile\mycode
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\NathanialPC\AppData\Local\go-build
set GOENV=C:\Users\NathanialPC\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=F:\personalFile\GoCode\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=F:\personalFile\GoCode
set GOPRIVATE=
set GOROOT=D:\GoLang
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=D:\GoLang\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.20.3
set GCCGO=gccgo
set GOAMD64=v3
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=0
set GOMOD=f:\personalFile\mycode\go.mod
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=C:\Users\NATHAN~1\AppData\Local\Temp\go-build4130307436=/tmp/go-build -gno-record-gcc-switches

Share the Go related settings you have added/edited

Run Preferences: Open Settings (JSON) command to open your settings.json file.
Share all the settings with the go. or ["go"] or gopls prefixes.

Describe the bug

this is my config.json

"version": "0.2.0",

"configurations": [
    {
        "name": "Launch",
        "type": "go",
        "request": "launch",
        "mode": "auto",
        "program":  "${workspaceRoot}",
        "cwd": "${workspaceRoot}",
        "logOutput": "dap",
        "showLog": true,
        "hideSystemGoroutines": true,
    }
]

I have a project, and it have the go.mod. Now I can execute "go build" build my project, but when I debug this project by vscode, prompt occurs :
Build Error: go build -o F:....\debug_bin.exe -gcflags all=-N -l . no Go files in F:....\ (exit status 1)

Steps to reproduce the behavior:

1. Go to 'run & debug'
2. Click on 'F5'
3. See error

Screenshots or recordings

If applicable, add screenshots or recordings to help explain your problem.

[John-zhan]

When I press F5 to debug my project, this prompt occurs. this project not in the GOPATH/src
Build Error: go build -o F:....\debug_bin.exe -gcflags all=-N -l . no Go files in F:....\ (exit status 1)

[hyangah]

@John-zhan Can you tell us more about the layout of your project?
Is your Go file in the F:.... directory? (I want to figure out which part was redacted).

[John-zhan]

Yep, my go.mod is in f：....\ ,and main.go in the f:....\main

[suzmue]

// todo: confirm the layout of files

To confirm, the files in your project are as follows:
f:...\go.mod
f:...\main\main.go

Are there any go files in f:...\go.mod? Could you also try starting debugging when you have main.go open?

[rohimsh]

I faced the same problem, which went away after :-

• updating the launch configuration from the following:

 "configurations": [
        {
            "name": "Launch Package",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "program": "${fileDirname}"
        }
    ]

to

    "configurations": [
        {
            "name": "Launch Package",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "program": "${workspaceFolder}"
        }
    ]

• ensuring the package name is main in my .go file

[SG1gdlJC]

I struggle to run a deep cleanup prior setup of go and VScode. Starting from regular un install to deeply search of folders and files placed no only on initial path but on app data and others. this is what was keeping something damaged

And by the way it is logical that there must a package named main and the file for it has to be saved on the project folder. if there is something missing on that this error might also arise but for user the un-installer of both apps and even extensions are incomplete

Manual and forced removal of residual folders for golang and vscode when errors remain.pdf

[RuthCodina]

y have the same problem, and this is my launch.json configuration

[RuthCodina]

I leave the comment in case it is useful for someone, but vstudioCode needs to know specifically where the main.go file is located, to enable debugging.

[mkDeveloper98]

I got the same error in my vscode project. Fixed it after providing correct path to main.go file in my launch.json file.
My main.go file was inside cmd folder. So the following change in the launch.json file fixed my issue.

    "configurations": [
        {
            "name": "Launch Package",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "program": "${workspaceFolder}/cmd"
        }
    ]

[RuthCodina]

I got the same error in my vscode project. Fixed it after providing correct path to main.go file in my launch.json file. My main.go file was inside cmd folder. So the following change in the launch.json file fixed my issue.

    "configurations": [
        {
            "name": "Launch Package",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "program": "${workspaceFolder}/cmd"
        }
    ]

Hi, yes the solution for me, was to add the "cmd":"${worksplaceFolder}" in "configurations"

{
    // 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": "Launch Package",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "program": "${workspaceFolder}/cmd/main.go",
            "cwd":"${workspaceFolder}"
        }
    ]
}

[lucastheisen]

I got the same error in my vscode project. Fixed it after providing correct path to main.go file in my launch.json file. My main.go file was inside cmd folder. So the following change in the launch.json file fixed my issue.

    "configurations": [
        {
            "name": "Launch Package",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "program": "${workspaceFolder}/cmd"
        }
    ]

Hi, yes the solution for me, was to add the "cmd":"${worksplaceFolder}" in "configurations"

{
    // 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": "Launch Package",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "program": "${workspaceFolder}/cmd/main.go",
            "cwd":"${workspaceFolder}"
        }
    ]
}

I think you meant: "... add the cwd" (instead of cmd). But also, once you add cwd you can use relative path for program:

    "configurations": [
        {
            "name": "myprog arg1",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "cwd": "${workspaceFolder}",
            "program": "./cmd/myprog",
            "args": [
                "arg1"
            ]
        }
    ]