4db6347e33
The gobind plugin exposes a set of Go packages as a AAR file ready to be used by and Android project. Unfortunately, being a library project limits the Go packages to access only the Java API from the standard library and the Android SDK. This CL tightens the integration with the Android plugin to support access to project dependencies such as the Android Support Library, to the generated R.* resource classes and finally to the Android databinding classes. When the gradle project has loaded the Android plugin, the generation of the Go library is split in two. First, the gobind tool generates the Java classes for the bound Go packages. In this step, Go packages can access the standard Java and Android libraries as well as project dependencies. After this step, Android databinding layout files can refer to Go classes. In step two, the gomobile tool generates the JNI libraries with the Go implementation of the generated Java classes. In this step, Go can access the standard Java and Android libraries, dependencies as well as R.* and generated databinding classes. Change-Id: If853ecabdbd01eec5f89d064a6bc715cb20a4d83 Reviewed-on: https://go-review.googlesource.com/30094 Reviewed-by: David Crawshaw <crawshaw@golang.org>
Go support for Mobile devices
The Go mobile repository holds packages and build tools for using Go on mobile platforms.
Package documentation as a starting point:
The Go Mobile project is experimental. Use this at your own risk. While we are working hard to improve it, neither Google nor the Go team can provide end-user support.
This is early work and installing the build system requires Go 1.5. Follow the instructions on golang.org/wiki/Mobile to install the gomobile command, build the basic and the bind example apps.
--
Contributions to Go are appreciated. See https://golang.org/doc/contribute.html.
- Bugs can be filed at the Go issue tracker.
- Feature requests should preliminary be discussed on golang-nuts mailing list.