Symlinking affects other programs using libudev.so.0 as well (and libudev.so.0 is not libudev.so.1 even though it's similar enough to make ToME work with it). Making a renamed copy into the specific ToME folder doesn't, as far as I know, so it's better to make a renamed copy. That's what my Gentoo-using programmer friend told me at least.
Another, safer but easy solution:
Workaround on 64-bit:
copy libudev.so.1 from /lib/x86_64-linux-gnu/ to the lib64 directory in your t-engine directory and rename the copy to libudev.so.0. In my case, the t-engine directory is:
/home/user/Desktop/t-engine4-linux64-1.2.5/
So, in my case, I just type this into terminal:
Code: Select all
cp /lib/x86_64-linux-gnu/libudev.so.1 /home/user/Desktop/t-engine4-linux64-1.2.5/lib64/ && cd /home/user/Desktop/t-engine4-linux64-1.2.5/lib64/ && mv libudev.so.1 libudev.so.0
It makes a copy of libudev.so.1 file to t-engine directory and renames the copy in t-engine directory to libudev.so.0. I don't know what libudev.so.x is but it seems libudev.so.1 substitutes libudev.so.0 as long as you rename it to libudev.so.0 to "fool" t-engine to think it is the missing libudev.so.0 by renaming it.
And I can execute t-engine successfully!
On 32-bit, the directory with libudev.so.1 is apparently /lib/i386-linux-gnu/ instead of /lib/x86_64-linux-gnu/