Building for iOS also fails even with ios build tag.

Interestingly, adding !android build tag also fails:

$ cat $GOPATH/src/github.com/hajimehoshi/gomobilebindtest/test.go 
// +build !android

package gomobilebindtest

func Foo() {}

$ gomobile bind github.com/hajimehoshi/gomobilebindtest
gomobile: package "github.com/hajimehoshi/gomobilebindtest": no buildable Go source files in /Users/hajimehoshi/go/src/github.com/hajimehoshi/gomobilebindtest

git bisect says golang/mobile@4600df5 is the cause

CC @eliasnaur

Yes, CL 99316 that you refer to changed gobind to be able to generate standalone bindings and changed gomobile to use that instead of its own complicated binding generator. That main benefit is that you can now avoid gomobile altogether for special needs. From the CL description:

"This greatly simplifies gomobile bind, but also paves the way to skip
gomobile bind entirely. For example:

$ gobind -outdir=$GOPATH golang.org/x/mobile/example/bind/hello
$ GOOS=android GOARCH=arm64 CC=<ndk-toolchain>/bin/clang go build -buildmode=c-shared -o libgobind.so gobind
$ ls libgobind.*
libgobind.h  libgobind.so

"

Another benefit is you can now run gobind -lang=objc,go,java some/pkg to generate a complete set of bindings for both platforms and check the result into version control.

To accomplish that without needing the Android and Xcode SDKs, gobind has to be platform neutral and as such will generate bindings without any particular GOOS or GOARCH set. If you need to vary the API, use the -tags flag to gomobile or gobind.

In summary, go install some/pkg will have to work before you can use gobind or gomobile bind on some/pkg.

The reason your !android example fails is that while bindings themselves are generated without GOOS/GOARCH set, they are set when gomobile builds the libraries for pkg.aar. So gobind will generate bindings for Foo, while gomobile will fail to find any Go files because GOOS=android. In summary, your exported API must be platform independent (or you can use tags to select variants), but your implementation can and will depend on GOOS/GOARCH.

Thank you for elaborating! I'm still not sure the implementation detail, but what I needed to do is to make the lib buildable both on mobile and non-mobile?

In further thought, your use case might still be possible. Could you try https://golang.org/cl/99777?

Change https://golang.org/cl/99777 mentions this issue: cmd/gomobile,cmd/gobind: allow per-platform bindings again

Yeah, with that patch, I've succeeded the experiment in the first comment:

$ cat $GOPATH/src/github.com/hajimehoshi/gomobilebindtest/test.go 
// +build android

package gomobilebindtest

func Foo() {}

$ gomobile bind github.com/hajimehoshi/gomobilebindtest