Designing a Kernel

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
User avatar
Touch
Member
Member
Posts: 56
Joined: Sun Oct 22, 2006 10:33 am
Location: England

Designing a Kernel

Post by Touch »

Well as you probably know, I'm starting to develop and code my kernel.

I just need to know one thing for now.

Let's say that I start the kernel, should I make it so that the kernel consists of %include? So the kernel is pretty much linked to all the other kernel parts.

e.g.

Code: Select all

%include "video.o"
%include ""system.o"
Is that a good way of setting it up, so that the kernel, just holds links to the other code?
"We cannot trust the sword in the hands of a n00b!" - Southpark
User avatar
bluecode
Member
Member
Posts: 202
Joined: Wed Nov 17, 2004 12:00 am
Location: Germany
Contact:

Post by bluecode »

Well, I'm not one of those "include everything in one file and then compile/assemble one file"-guy. I prefer splitting my code in several sourcefiles, that get compiled/assembled seperatly and are linked together to the kernel executable. The "glue" then are headerfiles, which declare functions/classes/makros and these can be included in source files. But I'm not sure how practicable this is with assembler (you plan to use assembler only?).

btw. assembler sourcecode normally does not come in *.o files. That's most likely an object file.
User avatar
Touch
Member
Member
Posts: 56
Joined: Sun Oct 22, 2006 10:33 am
Location: England

Post by Touch »

Yeah, I get you.

And the *.o was an example, I didn't think. It would be *.inc
"We cannot trust the sword in the hands of a n00b!" - Southpark
Post Reply