Skip to content

Latest commit

 

History

History
46 lines (29 loc) · 2.45 KB

Building.md

File metadata and controls

46 lines (29 loc) · 2.45 KB
Raw

Build configuration

DreamOS can be built using either gcc or clang toolchain.

This is controlled by the TOOLCHAIN variable, inside the Config.mk file, the accepted values are: gcc or clang.

PSF Font

The OS should be able to support both v1 and v2 PSF files. If running on linux there are a lot of PSF files available in: /usr/share/consolefonts.

They are stored compressed as .gz files, before using them with dreamos make sure to uncompress it. Then it has to be copied in the $FONTS folder and renamed as default.psf

If curious to know the version of the psf used, or explore the psf there is a handy tool for linux called gdbfed to tinker with the fonts. The sources are available here

Compilation

The following flags have to be properly set before building the os:

  • BUILD_FOLDER: this control the folder where all the output files from the build are placed. Default value is: dist
  • FONT_FOLDER: where to find the font for the kernel
  • ARCH_PREFIX: for now it only supports x86_64-elf, this will be used as prefix for the compiler and the linker.
  • FONTS: specify the folder where the font is stored.
  • IMAGE_BASE_NAME: the base name of the image (the full name will have also the ARCH_PREFIX variable, and a version number.

The above flags are present in the build/Config.mk folder.

Kernel related flags

They can change at any moment, or can be removed in the future

  • USE_FRAMEBUFFER if set to 1 it use the framebuffer video mode, if set to 0 it use the legacy VGA driver.
  • SMALL_PAGES if set to 1 the virtual memory will use 4k pages if set to 0 it will use 2mb pages
  • PIN_LOGO if set to 1 the dreamos logo will stay on the top right corner when the frambuffer is scrolling, otherwise will scroll up with the rest of the screen.

They are experimental temporary features, there are chances that they can be removed in the future.

Makefile Goals

Below the flags that are currently implemented to control the build/execution of the kernel:

  • build: Just build the os, and create the iso in $BUILD_FOLDER
  • run: It run the os using qemu
  • clean: To delete all build files
  • debug: To start the OS with the DEBUG flag active, it will print all messages on stdout, logging in Verbose mode
  • gdb: To start the OS with remote debugging mode enabled, to start the OS you need to connect using gdb and control execution from there.
  • tests: To run some kind of unit tests.