Hello Moritz,
since one week I am playing with the rexximage and try to execute it on Android directly. But it does not run correctly in my opinion. I have added some debug lines to see where the rexximage stops. Now I found out that the rexximage and rexx itself hang at the same location of code. In the Interpreter.hpp, there is a section where the Interpreter::getResourceLock() tries to lock the resource by calling the request() function of the SysMutex class. This method is called twice, in the first run it returns correctly and in the second run the program hangs while calling this request() method.
I searched for the Mudex implementation on Android and read that it should work well...
As I said, i have added some debugging - it is pushed to the Git repo (https://github.com/KlemensEngel/ooRexxForAndroid). Maybe you can take a look on that, you may have an idea what is going wrong ;-)
My Debug output:
root@generic:/ # ./data/local/oorexx/rexximage
Interpreter::startInterpreter - step 1
ResourceSection - step 1
SysMutex request()
SysMutex request() 1
ResourceSection - step 2
Interpreter::startInterpreter - step 2
Interpreter::startInterpreter - step 2-1
InterpreterInstance *Interpreter::createInterpreterInstance - step 1
ResourceSection - step 1
SysMutex request()
SysMutex request() 1
Interpreter::startInterpreter - step 1
ResourceSection - step 1
SysMutex request()
SysMutex request() 1
ResourceSection - step 2
Interpreter::startInterpreter - step 2
Interpreter::startInterpreter - step 2-1
InterpreterInstance *Interpreter::createInterpreterInstance - step 1
ResourceSection - step 1
SysMutex request()
SysMutex request() 1
Thanks, Klemens
Gesendet: Dienstag, 16. Februar 2016 um 09:04 Uhr
Von: "Moritz Hoffmann" <[email protected]>
An: "Open Object Rexx Developer Mailing List" <[email protected]>
Betreff: Re: [Oorexx-devel] oorexxforandroid - rexx.img
Von: "Moritz Hoffmann" <[email protected]>
An: "Open Object Rexx Developer Mailing List" <[email protected]>
Betreff: Re: [Oorexx-devel] oorexxforandroid - rexx.img
On Tue, Feb 16, 2016 at 7:18 AM, <[email protected]> wrote:
It seams the problem occurs when adding the custom target. What do you mean to try to run rexximage on Android. Just to execute the rexximage file?
Hi Klemens,
yes, that's the problem. rexximage is cross-compiled for the NDK's target, but it is part of the build process to run the rexximage executable, and the ooRexx cmake script is not capable of handling such situations (I can't even think of a clean solution). You can still run rexximage on Android, but you have to make sure it finds its files, such as CoreClasses.rex. It might be useful to add some debug output to your version of rexximage to figure out what files it tries to access as at this time the error reporting infrastructure might not be set up.
------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
