document the way to use gendex and dex.go for new GoNativeActivity.java behaviour #5387
Conversation
There was a problem hiding this comment.
FYI: We are planning on deprecating this tool here in favour of moving it into https://github.com/fyne-io/tools. I think I changed how the generation is done in that project.
| @@ -27,6 +27,11 @@ | |||
| import android.widget.TextView; | |||
| import android.widget.TextView.OnEditorActionListener; | |||
|
|
|||
| // GoNativeActivity is the java implementation that helps Go map to android via the NDK. | |||
There was a problem hiding this comment.
I'm not sure this first sentence is right - the activity is the entry point for our Android boot loader.
The NDK connects to this via C - so it's not really providing any connections itself I don't think?...
There was a problem hiding this comment.
What I meant (from my VERY limited understanding) is that it was the java SDK object that was a utility for Go to access via the C and the NDK.
I guess I don't know how to express it correctly :)
There was a problem hiding this comment.
Go accesses the Java object via NDK. The Java provides us certain functionality which is accessed through JNI and C functionality.
Is that clearer?
|
Ok. What's the new procedure to generate a new dex, then? |
We are in the process of moving |
No description provided.