#Cnc generals zh portable portable#
#Cnc generals zh portable software#
#Cnc generals zh portable code#

They want a continuation of the OS some of them started using 32 years ago which is compatible with the old software they still like to use. AmigaOS is about the passionate Amiga and Commodore fanbases. They could write something visually similar to AmigaOS and compatible with modern hardware but they crossed a point of no return so long ago, that abandoning that much work after so many years of development would be more devastating than maintaining of AmigaOS.Д¬reating an entirely new OS looking like Amiga Workbench would be missing the point entirely.

#Cnc generals zh portable code#

They sweat over very restricted source code to deliver things as basic as TCP/IP protocol.

#Cnc generals zh portable portable#

It can be made more portable by writing it against wrapper APIs that abstract the platform differences such as SDL, QT, wxWidgets and the like rather than against the platform API directly (plaforms such as windows, macos, linux, android and such).

Apart from calls to the platform API to do things like open files, enumerate directories and handle input, most of the game engine is portable and can be compiled against many platforms and CPU's and will behave the same (more or less). C++ on the other hand is always compiled to a real CPU machine code. Java in theory can be compiled once and then ran anywhere the JRE is available with some penalties usually in terms of performance because it is compiled to java byte code, machine code that doesn't have a physical machine that runs it, it is instead processed by a kind of virtual cpu that runs on different physical cpus (and is probably written in C or C++).

Your understanding of Java vs C++ portability is inaccurate. I have less interest in writing my own game engine than I do in making an version of an existing engine that can be ported to other operating systems and patched effectively to fix bugs the original developers/publishers never go around to. I can't guarantee it will get any further than the other attempts if I get burned out and I'm also working on RA++ as well.ДЄdditionally it will make documenting the file formats more accurately possible so it will provide additional resources for people to build modding tools for the game, though thankfully it is reasonably well covered already. You wouldn't be able to tell much difference right now of course, so from a player POV this isn't all that useful, but for development it makes it much easier to verify the new code behaves as expected. Good thing about this approach is that you could build the code and play the game now. There seems to be no end of attempts at an open source SAGE engine clone, this one is different to all the rest in that its attempting an accurate bottom up recreation like OpenRCT2, replacing the original game one function at a time until the entire thing is recreated in C++. I've not done any actual work on the way the in game view is rendered yet and I assure you I would rather ask people who knew more than me about it than spout nonsense on the wiki that I wasn't sure was accurate. I'll probably put a disclaimer on the main wiki page or something as we don't want misunderstandings like that to put people off contributing. The wiki is open for anyone to contribute to and unfortunately the project has an over zealous fan Zexaron who wrote those pages. If I didn't think it's a good effort I wouldn't have pitched in but instead would have just laughed about it.