Just conveying what coders say, can’t comment on which engines. But since Linux doesn’t care what binary it loads into memory to execute it doesn’t seem hard to support a translation layer.
I’m very curious what those coders meant! For what it’s worth, what you’re describing is essentially Proton and it has been extremely difficult to develop and requires a great deal of ongoing support. Cross-compiling is super hard, its the reason Android runs on (essentially) the JVM and that windows implemented UWP, and its the root cause behind driver compatability issues. I’m just not sure what you mean, I guess.
I assume since the Linux kernel doesn’t care what executable code gets run in memory, it was an engine that adda info for system call translations. Could be wrong, they did not elaborate.
Just conveying what coders say, can’t comment on which engines. But since Linux doesn’t care what binary it loads into memory to execute it doesn’t seem hard to support a translation layer.
I’m very curious what those coders meant! For what it’s worth, what you’re describing is essentially Proton and it has been extremely difficult to develop and requires a great deal of ongoing support. Cross-compiling is super hard, its the reason Android runs on (essentially) the JVM and that windows implemented UWP, and its the root cause behind driver compatability issues. I’m just not sure what you mean, I guess.
I assume since the Linux kernel doesn’t care what executable code gets run in memory, it was an engine that adda info for system call translations. Could be wrong, they did not elaborate.