Building for DOS, OS/2, and DOS on a MacBook Apple Silicon
retrocoding.net
retrocoding.net
Let's put up some description:
Carmack Jam! The most exciting Jam that requires you to follow the steps of a giant so that you can experience the thrills (and pains) of the 90s!
Path A: Humble path (Use C/C++ with SDL2 on a modern PC)
Competitors may use their own graphic resources, or read from the original game assets for bonus points!
Participants are not requested to produce a full game, rather, they are requested to produce a game engine with similar->full features comparing to the original game.
Here is the list of games to be produced (Only one game is required for Trilogies, Doubles or games with similar mechanics and looks)
- Wraith (or any turn-based, tile-scrolling Ultima spin-off)
- Dark Designs (or any blobber)
- Catacomb (or anything similar)
- Slordax (or any vertical scrolling shooter)
- Commander Keen (or any side scrolling platformer)
- Rescue Rover (Optional, I guess this does not hold too much technical improvement)
- Hovertank 3D (Optional, but maybe it's a good starter game for 3d stuffs)
- Catacomb 3D (Optional, it has textured mapping)
- Wolfenstein 3D
- Shadowcaster (Notice the increasing number of features of the 4 games)
- Doom
- Quake
Path B: Demi-God path (See description below)
Participants must use the original development environment. Real machines are given bonus points, while VMs are allowed. I'm actually not sure whether we have good NextStep VMs so maybe we should also allow Pentium machines using Windows NT, but it seems to be pretty far from the original development environment.
Please note that game development tools are also required to be coded on the original development environment.
Title currently reads:
> Building for DOS, OS/2, and DOS on a MacBook Apple Silicon
But from the content of the post it seems it should be
> Building for DOS, OS/2, and 16/32-bit Windows on a MacBook Apple Silicon
Which is what I did: https://github.com/depp/elf2dos.git
This is not really a polished, supported product, just a program I wrote to make DOS programs on Linux or Mac.
So you write a memcpy implementation, GCC figures this just copies memory and emits a call to memcpy!
A few weeks ago I gave it a chance out of curiosity because I wanted to run total comander and was pleasantly surprised of how well it worked which makes me think that it should be able to run openwatcom perfectly.
Side note: in the end, even though TC worked great I just crossed that item from my ToDo and continued using double commander (although the search feature is much better in TC).
I also do retro development on an Apple Silicon device, and like the author I built OpenWatcom so I could run it natively. I have it tied into the build system for the rest of my project and it works great.