Hi P.O., Sorry for the Late reply. I really dont think that this is any good. Android TV is an operating System based on Android but cut down to minimal Features for Multimedia streaming and so one. We would not be alle to test or run ooRexx on it.
In we want to try ooRexx on a device it would have to be a smart phone or Android Running on a Virtual machine like yours. To get back to your VM's. I still havent figured out how to Transfer files to the VM. But im working on the APK (Package to install an App in Android) as soon it is available I will contact you and we will figure out a way to install my apk. Best regards Thomas ________________________________ Von: P. O. Jonsson <oor...@jonases.se> Gesendet: Sonntag, Dezember 10, 2023 1:40 PM An: Open Object Rexx Developer Mailing List <oorexx-devel@lists.sourceforge.net> Betreff: Re: [Oorexx-devel] Update on ooRexx -> Android Hi Thomas, What would be a good platform for testing, something like this? <https://www.googleadservices.com/pagead/aclk?sa=L&ai=DChcSEwi1rP7k7oSDAxUUxNUKHfQZAQ0YABATGgJ3cw&ae=2&sph=&ohost=www.google.com&cid=CAASJeRoLPSNj9hindG1uxLlCqAlSHUhfeOgLAKzskSj0x-Tnr9NHzQ&sig=AOD64_0SMi_tHf1xpbIoGo7FSuyRYZE2Dw&ctype=5&q=&ved=2ahUKEwiNzPfk7oSDAxUcSfEDHXx9CdsQwg8oAHoECAUQMw&adurl=> [41o2ixAoxAL._SR600,315_PIWhiteStrip,BottomLeft,0,35_PIStarRatingTHREEANDHALF,BottomLeft,360,-6_SR600,315_ZA31,445,290,400,400,AmazonEmberBold,12,4,0,0,5_SCLZZZZZZZ_FMpng_BG255,255,255.jpg] Android 13.0 TV Box 4GB RAM 64GB ROM，TV Box Android mit RK3528 Quad-Core 64bit Cortex-A53 chip，Smart TV Box 8K UHD Videos,2.4G/5G Dual WiFi Bluetooth 5.0 mit kabelloser Mini-Tastatur,Schwarz<https://www.googleadservices.com/pagead/aclk?sa=L&ai=DChcSEwi1rP7k7oSDAxUUxNUKHfQZAQ0YABATGgJ3cw&ae=2&sph=&ohost=www.google.com&cid=CAASJeRoLPSNj9hindG1uxLlCqAlSHUhfeOgLAKzskSj0x-Tnr9NHzQ&sig=AOD64_0SMi_tHf1xpbIoGo7FSuyRYZE2Dw&ctype=5&q=&ved=2ahUKEwiNzPfk7oSDAxUcSfEDHXx9CdsQwg8oAHoECAUQMw&adurl=> googleadservices.com<https://www.googleadservices.com/pagead/aclk?sa=L&ai=DChcSEwi1rP7k7oSDAxUUxNUKHfQZAQ0YABATGgJ3cw&ae=2&sph=&ohost=www.google.com&cid=CAASJeRoLPSNj9hindG1uxLlCqAlSHUhfeOgLAKzskSj0x-Tnr9NHzQ&sig=AOD64_0SMi_tHf1xpbIoGo7FSuyRYZE2Dw&ctype=5&q=&ved=2ahUKEwiNzPfk7oSDAxUcSfEDHXx9CdsQwg8oAHoECAUQMw&adurl=> Any advice welcome Von meinem iPhone gesendet Am 10.12.2023 um 12:24 schrieb Erich Steinböck <erich.steinbo...@gmail.com>: 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? _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
