Re: Helping Euphoria ideas

new topic     » goto parent     » topic index » view thread      » older message » newer message
said...

Getting a native Android app and package (apk) is a bit more effort, but don't be too surprised if it happens in the near future.

This could be done in a few different ways:

  • The entire application is written in Euphoria (as a native activity), translated into C and built with the NDK build system. A small wrapper might be necessary around the generated C code, since the signature for an Android native activity entry point is "void android_main(struct android_app* state)". And of course neither the application nor the Eu runtime can use APIs that aren't available on Android.
  • The Eu code is built into a shared object which can be used by the Java part of your app. That is, translate to C with the -so switch, and then generate some JNI glue that allows the library's code to interface with Java (preferably automatically. SWIG..?).
  • A full Eu interpreter is packaged into a shared object complete with a JNI layer and allows any Android app using that library to execute (interpreted) Eu code.
new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu