My project structure is like this.
packagetest/
main.go
lib.go
In main.go
, I have this code.
package main
import "fmt"
func main() {
fmt.Println("Hello from main.go.")
Test()
}
While in lib.go
, I have this code.
package main
import "fmt"
func Test() {
fmt.Println("This is the Test function in lib.go.")
}
When I try to compile with go build main.go
, I get ./main.go:7: undefined: Test
. Is this way of structuring my code possible?
Try running just go build
. When you give it a go file as an argument, it will not look for other go files. You can also do go build *.go
This is an old post but it didn't answer my issue clearly, so I'm posting for the benefit of others in the future.
When run go run --help
you will find this manual:
Run compiles and runs the main package comprising the named Go source files. A Go source file is defined to be a file ending in a literal ".go" suffix.
By default, 'go run' runs the compiled binary directly: 'a.out arguments...'.
go run <filename.go>
is used for small programs with just a few files. With several files you will run into an issue where your main.go
cannot find other files because go run
doesn't compile and link them implicitly unless named. That's why go build
the project works.
Alternatively, go run *.go
(building all files) should work most of the time.
On the golang.org webpage you can read about the build
command that:
If the arguments are a list of .go files, build treats them as a list of source files specifying a single package.
So, go build main.go
will treat main.go as a single package. Instead, you should use:
go build
to include all files in the folder.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With