I’m just starting with Xojo and I’m having real trouble in getting the built applications to run on my PI.
Raspberry Pi is 3b+ with latest Raspbian Stretch
I believe I have configured everything according to the guides (Rasberry Pi Book, Youtube videos and the minimum requirements etc) but the executable still does not want to run from my Pi desktop. I get the option to “Execute” or “Execute in Terminal” but it just drops back to the desktop with no errors to work on.
I can build the app in Xojo fine, I then FTP the executable and libraries folder to my desktop (so not using the run remotely option). Set the file as executable but it still does nothing.
I’ve tried with the example executables (XojoNotes and other examples) so its not the application. I have installed libunwind8 as per the guides.
I’d be most grateful for any guidance as I’m really starting to pull my hair out with this. I realise that there is not much to go on here but hopefully someone on here may have seen this behaviour before.
As my initial post states I did set the file as executable. What I did was use the properties/permissions in the GUI and set ‘Execute’ to ‘AnyOne’ rather than any command line. Is that what you are suggesting?
Although I didn’t set the Libraries folder/files to execute, I wonder if that could be it?
I have libunwind8 installed (as per the Xojo guide)
Execute is enabled on all files and the Libraries Folder
Ran the Executable from a console window (launched from the desktop) and I get “Segmentation fault”
Ran ldd /home/pi/Desktop/XojoNotes/XojoNotes , as you suggested Derk, and I get “not a dynamic executable”
The “not a dynamic executable” is tarting to make me think there is something wrong with the compile but I can confirm that the Build Settings within Xojo is set to Linux and ARM 32-bit.
I really I hope I’m not doing something really dumb here.
And just for completeness, I just checked, setting the transfer mode to “Binary” in my FTP client (I use Filezilla) also works. I don’t need to zip up the file if I use Binary mode, it just works.
obviously ASCII mode does something to the file that renders it useless
probably translates line endings which would be VERY significant for an executable as that could be part of an instruction that got whacked and that would ruin the executable (ie. if you’re on Windows and line endings could get translated to Unix)
binary just sends those exact bytes without trying to do any translation