summaryrefslogtreecommitdiff
path: root/lpsolve
diff options
context:
space:
mode:
authorTor Lillqvist <tlillqvist@suse.com>2011-11-15 01:41:57 +0200
committerTor Lillqvist <tlillqvist@suse.com>2011-11-15 01:54:49 +0200
commit2bf110d691053353d6cb06ad2bbd1b78fef60f19 (patch)
tree159fcfed4e1d335f65a1e17802a2445a7cfe2487 /lpsolve
parentd14416463a0e62cf624cf66e8a599abac5694cd2 (diff)
Rework the bootstrap mechanism of a LO program on Android
Do use NativeActivity and android_native_app_glue after all. I hope this enables us to have a "message pump" (a loop that typically would call ALooper_pollAll()) inside the LO "program" being run, as expected by LO code. (On Android, a "program", even one mostly implemented in native code, is actually a shared library loaded by the main Java code of an app.) The android_native_app_glue code and the android_main() it calls belongs in the bootstrap library, though. Not in SAL_MAIN_IMPL. The earlier idea, having a "normal" Java Activity subclass, would mean events come in as method calls to that class. To then turn those into something the LO code can "get", we would have effectively had to re-implement what android_native_app_glue does anyway.
Diffstat (limited to 'lpsolve')
0 files changed, 0 insertions, 0 deletions