1.0.0.alpha#201 Fails to build from Run/Debug Configurations

[nwaywood]

I have a project with two files in package main.

When I try to build the application using the Run/Debug Configurations it fails because it can't 'see' the handler functions from handlers.go (func main() is in wiki.go).

There is nothing wrong with the application because it works when I run go install && gowiki from the command line.

I am using WebStorm 9.0.3.

[dlsniper]

Can you also provide what configuration you have for File | Settings | Languages & Frameworks | Go Libraries and where's your go sdk (goroot)? also, if you execute from the command like the same command, /usr/local/go/bin/go build -o output_file_path /Users/nick/.../wiki.go what does it happen? Also which Run option have you used to run the command?

[nwaywood]

Here is my configuration for Go Libraries:

The first path in the above image is my GOPATH and the second is GOROOT.

I get the same output when I execute /usr/local/go/bin/go build -o output_file_path /Users/nick/.../wiki.go from command line.

I don't know exactly what you mean by "Also which Run option have you used to run the command?", but here is a screenshot of my Run/Debug Configurations

[dlsniper]

I see two problems:

• you should remove GOROOT from Go Libraries, that's not needed and it shouldn't be there (there's no such guidance in the readme page afaik, please read the readmes when you try alpha versions ;) )
• if go build outputs the same problem, then the problem is not in the plugin, it's somewhere else.

What do you get if you run go env?

[nwaywood]

Ok

• I just removed GOROOT from Go Libraries as you suggested, I think I put it in there out of desperation once when I was trying to get something to work. Sorry about that.
• I probably should note that the problem only started happening once I refactored the application into 2 files, WebStorm built the application successfully when all of package main was in wiki.go
• Here is my output from go env

GOARCH="amd64"
GOBIN=""
GOCHAR="6"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/nick/Documents/code/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common"
CXX="clang++"
CGO_ENABLED="1"

[dlsniper]

I'd recommend reading the following links:

• https://golang.org/doc/code.html
• http://blog.golang.org/organizing-go-code

Also I'd highly recommend moving the second file contents to its own package as it makes things easier to maintain and more in line with the Go expectations.

Still, if you want to keep multiple files for the same main package, you need to specify them to the go tool such as go run handlers.go wiki.go where as go run wiki.go won't run (just as go build wikil.go won't work). go build without any arguments will however properly build the app itself.

@zolotov I'll leave this open and up to you to consider for the runner configuration. The issue is that the go tool expects all the files to be fed to it in this particular case, when there are multiple files in the main package or go build should be ran directly, without the specific file. I have no data to support the numbers behind it but, at least to the go rules, this doesn't seem to be a popular form of organizing the code.

[zolotov]

@dlsniper thanks, I'll leave it open for a while as a test case of building

@niwaywood since go install works for you could you show me the output of go install -x please? Just to known what go build does in your case.

[nwaywood]

Thanks for the feedback, I have already read the two links you mentioned and I would argue that having multiple files in package main goes against Go expectations. The way I see it is that application specific code should refactored into files and non-application specific code should be refactored into libraries. This may come down to personal preference but I just had a look at some open source applications and it seems having multiple package main files is quite popular, for example:

• https://github.com/jingweno/nut
• https://github.com/tools/godep

Whether its a popular pattern or not I feel the plugin should still allow it.

@zolotov here is the output of go install -x:

WORK=/var/folders/hf/9hd4pxw10pv4vgp8ts25rhdc0000gn/T/go-build502833202

[nwaywood]

@dlsniper you said

"Still, if you want to keep multiple files for the same main package, you need to specify them to the go tool such as go run handlers.go wiki.go where as go run wiki.go won't run"

I understand that, but (correct me if I'm wrong) you can't specify extra run parameters like that from the Run/Debug Configurations. Meaning that there is still no way to do this with the plugin/WebStorm. Is this correct or am I missing something?