LibC requirements for porting DOOM?

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
UnmappedStack
Posts: 1
Joined: Thu Oct 17, 2024 7:27 pm

LibC requirements for porting DOOM?

Post by UnmappedStack »

Hi all, long time reader, first time poster :D I've finally gotten to a point where my kernel is able to run a very basic user space shell with devices etc, and while I take a break from SMP which has been quite annoying me, I want to implement a proper libc, with the hopes of eventually porting DOOM.

From what I understand, doomgeneric is very easy to port, only requiring a libc and just a few platform specific functions. Does anybody who's implemented this before have a list of functions, typedefs, and macros needed in the libc to be able to port DOOM, and what exactly it requires? Thank you! :)
MichaelPetch
Member
Member
Posts: 797
Joined: Fri Aug 26, 2016 1:41 pm
Libera.chat IRC: mpetch

Re: LibC requirements for porting DOOM?

Post by MichaelPetch »

Off topic: Back in the mid 80s I remember listening to Larry King Live on shortwave radio and calling into his show (he had John Dvorak on) and had the opportunity to use the "long time listener, first time caller!" for the first time.
cloudapio
Posts: 3
Joined: Sun Feb 11, 2024 11:46 am

Re: LibC requirements for porting DOOM?

Post by cloudapio »

Usually, to find out what libc functions a third-party port requires, I'd recommend trying to build the program, seeing where the compilation fails, and implement whatever it needs, and so on. That's what I did, in any case.

As for platform-specific functions, the doomgeneric README covers those well: https://github.com/ozkl/doomgeneric
Post Reply