Hi Thomas,
the CMake config issues seem to be fixed. Found and not found configs look reasonable.
I'm not aware of any other ooRexx cross-compile attempt, so this is new territory for us.
To complete your build you can try commenting out the six lines after # Build the rexx.img file
and add a line
message(STATUS "rexximage ${ORX_IMAGE_OUTPUT_LOCATION}/rexx.img")
When the build has completed you can run the built rexximage executable in an Android shell.
The above message will show you which argument you should supply (although the path might be different between what your compile host sees and what the Android shell sees).
Moving an existing rexx.img might also work as long as host and Android are the same bitness and architecture.
Are you cross-building for a different architecture, like from x86 to ARM?
Does the cross build allow building Android 32 bit (when your host is 64 bit)?
Do you run the Android code on an Emulator or are you pushing the build artifacts to an actual Android hardware?
Did you note down the steps necessary to successfully set up Android NDK and Emulator for an ooRexx cross-compile? If yes, can you share the them?
