Years ago I created a linux executable with Xojo (formerly RealBasic) that would compile to a single file, let us call it Test. From a PHP script I could launch that executable with a command like this:
Later Xojo started building executables with an external folder named Test Libs that holds needed libraries instead of embedding them in the executable itself. With this new architecture, I can no longer launch the linux executable from a PHP script.
I have tried creating a console app, but still stores library files in the external Libs folder so they cannot be found when launching the executable from a PHP script.
I tried sudo to launch the executable with the root password, but that also fails to find the libraries.
Any ideas on how to launch a Xojo generated linux executable from PHP?
Rename “XYZ Libs” to just “Libs” and try again. I had something like that in the past with Windows and the work around was this. Maybe related. If that does not help, check if the entire path includes non-ascii codes, like international chars like ç ã ü …
It appears as if a Xojo linux executable uses some mechanism to locate its libraries files and that mechanism isn’t available when launched from PHP. It would seem that the Xojo people could document some kind of environment variable or something to make this work.
I just created a fresh XYZ do nothing linux app with a XYZ Libs folder using Xojo 2020 and now I can launch it from a PHP script. Now I’m trying to isolate why the real executable works with old RealBasic but fails with new Xojo.
I think I have sorted it out. Years ago when Xojo began storing the library files externally I think there may have been an issue with the executable not finding the libraries. That now works fine with the new Xojo. Due to a deprecated feature in my old App, I had to make a change to compile with the new Xojo that introduced an exception during launch.