(18-02-2020, 01:23 PM)josemendez Wrote: Hi there,
You can build a executable in any other platform, and then run it in linux. It will work, the issue seems to be in the editor itself.
For some reason, the editor isn't either looking for the library in the correct folder, or copying it to the folder where it expects plugins to be located. According to your log, this is where the editor is looking for it:
/home/vagrant/Unity/Hub/Editor/2019.3.0f6/Editor/Data/Mono/lib/libOni
/home/vagrant/Unity/Hub/Editor/2019.3.0f6/Editor/Data/Mono/lib/libOni.so
Obviously, the plugin cannot be located in the editor's own files, but in the project files. I don't know why the editor is looking for plugins in its own files. I suspect this is a bug in Unity, as no other platform -including some linux distros- have this problem.
Next thing I'd try is copying /Assets/Obi/Plugins/x86_64/libOni.so to /home/vagrant/Unity/Hub/Editor/2019.3.0f6/Editor/Data/Mono/lib/, as that's where the editor is (wrongfully) looking for it.
Let me know how it goes,
First, thanks for the quick reply.
Happy to see that I can build on my Mac and run on the Linux machine, that will hopefully do as an interim solution at least.
But still, would be great to have this figured out. Trying to do what you ask me to do makes me realise that Unity have changed their file structure from 2019.2 to 2019.3, now there is no longer a /Unity/Hub/Editor/[unityVersion]/Editor/Data/Mono folder but instead /Unity/Hub/Editor/[unityVersion]/Editor/Data/MonoBleedingEdge as well as /Unity/Hub/Editor/[unityVersion]/Editor/Data/MonoEmbededRuntime, the former the only one including a /lib subfolder. Copying in the libOni.so file to that location makes no difference however...
However, maybe this structural change can help explain the error?
Let me know if you have more ideas on how to solve this issue.