In both cases, using a language that has a cross platform dependency manager eliminates a huge number of compatibility problems. Even if you don't, the Linux community will do most of the debugging for you and submit fairly detailed bugs (failed on platform X with error Y, workaround Z produces different error), so all you need to do is interact with the community periodically, fixing the easy issues to keep people happy.įor FOSS projects, everything gets easier once you get it accepted in the package repositories, and if your project is popular enough, you can usually get someone else to do it for you. Steam does this and it works pretty well. The way developers solve this on Windows works on Linux: ship the libraries you need with your application. It just never crosses their mind to do it differently. I think a lot of games fail to work on Linux not because of the support costs or the platform fragmentation, but because the developers just don’t care or they choose engines and technologies that are not cross platform. A totally unsupported build is at least better for Linux users than abandoning the platform entirely.
ROCKET LEAGUE MAC OS TORRENT HOW TO
Then just fling off a “totally unsupported Linux build”, stick it on an FTP server, ignore support tickets mentioning Linux, and let the Linux people figure out how to get it working-they will! Let them figure out their driver problems or which distributions ship the right library dependencies. It shouldn’t take that much longer to use platform-neutral APIs than the Windows-only equivalents. If you develop it from the start as cross platform, then it shouldn’t be some gargantuan effort to port it. Develop the game targeting Windows, and simply don’t do the things that unportably tie it to Windows. you don't need to do additional work to get your gaming running on Linux.
0 kommentar(er)
