It’s funny when information from one person’s build system leaks like this - I once had a coworker who named his hard drive “Sh*tHead” which occasionally led to some interesting bug reports
Ok, instead of double clicking the ide to start it, open a terminal window, type open , drop the Xojo.app bundle into the terminal window and press return. The ide will launch and spew a bunch of console messages. Once the ide launches, go to the terminal window and press CMD-K to clear the window. Now create a web project and compile it for Linux ARM. Im curious if you get any errors there.
Firts clear the xojo cache, in preferences - builds. Then quit xojo completely. remove the plugins, re-download and reinstall them in the plugins folder.open xojo again.
Then make sure to select ARM 32 for linux builds.
I’ve been corresponding with Dave via email, and apparently this issue is with the Chilkat module built for ARM 32. I don’t know the solution, but maybe if Xojo and Chilkat share notes about LLVM compiler/linker versions and options, we might sort it out.
In other words, I’m going to show the compile and link options Chilkat uses to build the shared lib, and maybe Xojo can share the same for how a Xojo application is built. If both are the same, then one would think there would be no trouble when the .exe tries to load the shared lib…
Chilkat compiles its sources (for Xojo ARM 32) like this: