Raven runs Windows applications on Linux. You install them with their own installers, the same ones you would use on a PC, and they start: no virtual machine, no winetricks, no DLL overrides.
Raven runs Windows applications on Linux. You install them with their own installers, the same ones you would use on a PC, and they start: no virtual machine, no winetricks, no DLL overrides.
It’s still unclear where the “Raven’s guest components or libraries” come from… which I think it’s the question that was being asked (given that wine is a reimplementation of the Windows components).
EDIT: apparently they are using ReactOS implementation of the Windows kernel & system libraries to translate the system calls, and beyond that they use the official Microsoft libraries that need to be installed inside the Raven runtime, like you would install in ReactOS.
EDIT2: Also apparently there’s some controversy going on because ReactOS is GPL but Raven is getting distributed as MIT, so there’s a bit of a mix of licenses which opened a bit of a debate.
Thanks for your reply, wasn’t sure if it was just a new WINE mod or its own thing (just similar in some elements like prefix and dot folder stuff). It is kind of awesome that part of ReactOS is being used while the main OS is still not ready.
Oh awesome, I had misunderstood that paragraph as it being a VM solution like Winboat, but your clarification makes the project much more exciting
Raven relicensed to gpvl3 now.
https://github.com/mirkobrombin/raven/blob/main/LICENSE