"Demicrosoftizing" FiveM

[Pained_Psyche]

@nta

functional goal of running on non-Win32/desktop platforms should be irrespective of ‘using any MSFT tech’.

@nta

A lot of this makes no sense when you start to think of a functional goal: .NET/C# stuff is required to remain for functional compatibility with servers and already works on non-Windows platforms, PowerShell is cross-platform ever since .NET is, removing ‘Windows-specific headers’ would make for something not working on Windows at all, and ‘cmd/bat’ is also going to make your fork entirely useless on Windows and also lead to an entirely different functional goal.

What I meant by removing/replacing was actually adding native, functional equivalents so MSFT tech (like Powershell) does not have to be installed.

Ideally, I’d see platform-agnostic project definition (which seems to be there already in form of premake) and a separate set of build scripts (for every supported platform) written in whatever shell scripting language is native to that platform (sh/bash for Linux, batch/PS for Windows) that makes use of that definition to generate project files for a toolchain native to that platform (unix makefiles for Linux, VS solution/MSBuild for Windows).

@nta

Curious choice of starting point, especially as a) it only wraps a few lines of manual command and b) it’d be perfectly viable to make these helpers work on PSCore, even if it’s not very necessary for initial functional portability.

This is a massive project developed over several years. For anyone who did not take part in it’s development and does not know it inside out (or almost at all for that matter), the only logical course of action would be to start “at the beginning” and that’s where the entry point seems to be.

@nta

Odd assumption, a lot of the code here can be #if 0’d as it’s not important for initializing execution, the other parts are relatively trivial to get to work as seen in the Android port of CitiLaunch.

As seen is a rather unfortunate choice of words here, since I have asked to see and was denied.

It is somewhat difficult for me to discern which parts aren’t important and can be safely #if 0'd without immediate replacement and which can’t.

@nta

If you want a porting effort to succeed, it’s a good start to try to hit one goal at a time, and that wouldn’t be the ideological concerns: rather trying to get ExecutableLoader or similar working without any components loaded, so the game itself can run in a compatibility layer of whatever sorts (whether it be Winelib, Rotor, a custom layer, or whatnot), and then slowly porting the usual dependency tree of game-dependent components upwards (rage:allocator, rage:device, rage:graphics, etc.).

Now this is definitely very useful, clear and actionable advice. Thank you.