Can't build for Windows from Darwin with Go 1.16

[unquabain]

My project builds and runs on Darwin using Go 1.16. But when I use fyne-cross to build a Windows binary, several dependency libraries fail to compile because—it appears—the Go version in the Docker containers are older.

From the output:

api/authenticate.go:77:16: undefined: io.ReadAll
api/diagnostics.go:44:16: undefined: io.ReadAll
note: module requires Go 1.16
# github.com/xuri/excelize/v2
/go/pkg/mod/github.com/xuri/excelize/v2@v2.4.1/calc.go:1907:18: undefined: strconv.ParseComplex
/go/pkg/mod/github.com/xuri/excelize/v2@v2.4.1/calc.go:1923:18: undefined: strconv.ParseComplex
/go/pkg/mod/github.com/xuri/excelize/v2@v2.4.1/calc.go:1939:18: undefined: strconv.ParseComplex
/go/pkg/mod/github.com/xuri/excelize/v2@v2.4.1/calc.go:1955:18: undefined: strconv.ParseComplex
/go/pkg/mod/github.com/xuri/excelize/v2@v2.4.1/calc.go:1971:18: undefined: strconv.ParseComplex
/go/pkg/mod/github.com/xuri/excelize/v2@v2.4.1/calc.go:1987:18: undefined: strconv.ParseComplex
/go/pkg/mod/github.com/xuri/excelize/v2@v2.4.1/calc.go:2003:18: undefined: strconv.ParseComplex
/go/pkg/mod/github.com/xuri/excelize/v2@v2.4.1/calc.go:2019:18: undefined: strconv.ParseComplex
/go/pkg/mod/github.com/xuri/excelize/v2@v2.4.1/calc.go:2039:18: undefined: strconv.ParseComplex
/go/pkg/mod/github.com/xuri/excelize/v2@v2.4.1/calc.go:2059:19: undefined: strconv.ParseComplex
/go/pkg/mod/github.com/xuri/excelize/v2@v2.4.1/calc.go:2059:19: too many errors
note: module requires Go 1.15
[✗] exit status 2

I can update the version of Go in a running fyne-cross docker container, but how can I tell the fyne-cross command to use my own container or image?

[Jacalz]

The latest release does have Go 1.16 inside the containers. Are you sure that you have the latest release installed and the latest images pulled?

You can install the latest fyne-cross using go install github.com/fyne-io/fyne-cross@latest and pulling the latest images using fyne-cross windows —pull.

[lucor]

@unquabain did you had a chance to test the steps suggested by @Jacalz ?

[Jacalz]

@unquabain Can you still reproduce this using the steps mentioned above?

[andydotxyz]

Many updates have been applied since this ticket, closing