BarinkOS/superVisorTerminal.h at 2bcc79216e52769b542ed2d7df4cfaf3c20fdb27 - BarinkOS - Barink.dev [GIT]

Nigel/BarinkOS

Nigel b07b4f0d38 Moving certain aspects into their own static library

Problem:
	As our kernel grows we need more complex datastructures and functions these would come from
	the standard C/C++ library with normal programs.
	The kernel is a freestanding programme and has no access to standard libraries.

Solution:
	We build a mini version of the standard C/C++ library which will contain the
	datastructures and functions we want. This library can then be statically linked
	into our kernel binary.

	Making it a statically linked library also gives more structure to the project.
	Keeping these random functions and datastructures in the kernel just clutters the
	kernel source code with less relevant source code.

2023-02-19 23:38:32 +01:00

9 lines

252 B

C

Raw Blame History

 #pragma once
 #include "../terminal/kterm.h"
 #include "../time.h"
 #include "../drivers/pit/pit.h"
 #include "../drivers/ps-2/keyboard.h"
 #include "../memory/PhysicalMemoryManager.h"
 #include <CoreLib/Memory.h>
 extern "C" void startSuperVisorTerminal();