Go Bare Bones: Difference between revisions

The first thing you should do is set up a GCCGoGCC Cross Compiler that supports Go. To do this read and follow [[GCC Cross-Compiler]] to the letter with one exception. When configuring the build for GCC we need to enable Go to get the i686-elf-gccgo compiler.

* <package name>.gox

* <package name>.so

* <package name>.a

* <package name>.o

InA our.gox examplefile it will notcontains findjust the import data as we name our output file terminal.go.o instead of terminal.go to showIf you howwanted to solve an issue like this. To solveextract it wefrom can easily extract the import data fromour terminal.go.o into a newobject file calledwe terminal.gox usinguse: <source lang="bash">i686-elf-objcopy -j .go_export terminal.go.o terminal.gox</source>

Now we create the file kernel.go that containdcontains the Main() function called from our bootstrap assembly we've already created and compiled above. It will import the terminal package we also created & compiled and extracted the import data file from. Then we use that package to print our text to the screen.

The file myos.bin is now your kernel. Note that we are linking against [[libgcc]], which implements various runtime routines that your cross-compiler depends on. Leaving it out will give you problems in the future.

Virtual Machines are very useful for developmentdeveloping operating systems, as they allow you to quickly test your code and have access to the source code during the execution. Otherwise, you would be in for an endless cycle of reboots that would only annoy you. They start very quickly, especially combined with small operating systems such as ours.