GO issue. File undefined

[ant-druha]

From the user feedback:

Hello, I am trying to use the GO plugin. I have an app that has a directory with approx 20 go files all under package main. I have setup the the intellij config as "Go single File". I try to run the app and it compiles my main.go but then it complains about not finding other types/funcs in the other go files in the same dir. This app compiles fine with go run *.go

Here is a sample project with 2 go files https://dl.dropboxusercontent.com/u/6595319/gotest.zip https://dl.dropboxusercontent.com/u/6595319/gotest.zip

I cannot get this to work

[dlsniper]

For that case the run configuration should be of type Go Application with a package as run kind not file. As the name says, Go Single File run configuration is dedicated to running a single file.

I hope this helps.

[kolkov]

It's work, but not intuitive... ((

[dlsniper]

@mistbow-git how do you usually execute the project? That way it could help the plugin get better at it.

[mmargerumImpactrx]

I switched my project from "single file" to "go application" and I chose "run kind package"

I assume I should put "main" for the package setting? When I do this I see "Error: cannot find package main"

I think the issue may be that I do not have the go files inside of the src directory inside the root of this project file.

[mmargerumImpactrx]

once I placed the files inside a src directory and added my root project directory to the "project libraries" in the "Go libraries" prefs, it picked up the other go files and the app runs now.

[zolotov]

I assume I should put "main" for the package setting? When I do this I see "Error: cannot find package main"

You get the same message if you run go build form terminal because your project wasn't in GOPATH.

I think the issue may be that I do not have the go files inside of the src directory inside the root of this project file.

Indeed, but plugin has nothing to do with it, it's actually golang workspace requirement: https://golang.org/doc/code.html#Workspaces

[margerum]

No I was able to go build and go run the project from the command line without modify any go path.

[margerum]

I do agree though that I should be following the recommended structure for projects. Thanks

[zolotov]

No I was able to go build and go run the project from the command line without modify any go path.

You can do this only for building by files. For package building you have to have proper GOPATH, otherwise gobuild cannot find target package by its import path.

[margerum]

Right I'm effectively doing a multi file build using package main. That's what was confusing me because I'm not building a package.

[zolotov]

@margerum I see. Please follow for updates of #2013, I think I can add multifile run support as part of that issue