I'm inclined to say a Service would be better for Context access instead of
a noop Activity. You should be able to make the Service instantiate needed
resources or provide an implementation to instantiate those resources and a
method for communicating that logic in Go. If you don't want parallel
ve
As it stands now, we have a pure java wrapper application that simply starts a
subprocess with our pure go binary. I guess what you are saying is that our Go
application needs to become a library, rather than a process. Which is
complicated as I am not sure it can, as our cleanup assumes the pro
How were you intending to run the Go program?
iirc you'll need access to a Context that can only be provided by the
Dalvik VM, and that can only be instantiated via bytecode ran on the VM (so
use Java). The first entry point this is provided is Application.onCreate
when said class is declared in t
Your example has a MainActivity.java.
As I said, this is a Go application, and as it stands it has no Java, so it
doesn't have (and doesn't intend to have) a main activity.
Also, your initialization (Hello.initContentProvider) happens from Java
(not from Go), so my question is still unanswered of
