Spexeah/Asuro

1 Fork 0

Files

T

t3hn3rd dd3bb1e016

continuous-integration/drone/push Build is passing

Details

continuous-integration/drone/pr Build is passing

Details

Automate boot unit inclusion with architecture-aware Moderne analysis

- Replace boot.mgr's static unit list with generated dangling_units.inc
- Generate Pascal LSTs and run the dangling-unit recipe before compilation
- Exclude Wasuro, inactive architectures, and NOT_DANGLING units
- Add ASURO_ARCH selection with an x86 default
- Mark unfinished legacy units as NOT_DANGLING
- Inherit pinned Moderne tooling in the builder image
- Ensure Drone pulls the latest builder image
- Document the updated build pipeline in MkDocs

Validation:
- Full x86 ISO build and VirtualBox boot succeeded
- 1,133 kernel tests passed with no failures
- x86_64 build failed clearly due to unavailable sources

2026-11-07 21:49:06 +00:00

4.1 KiB

Raw Blame History

Asuro

We welcome everyone to give building/breaking/fixing/shooting Asuro a go, feel free to follow the steps below and mess with Asuro for fun or profit.

Setting up your build environment

Prerequisites

WSL2 WSL2 is used in conjunction with Docker to predefine a build environment for Asuro.
Docker for Windows Docker is used to ensure a predefined environment with the correct versions of; Freepascal, Binutils, NASM, Make, xorriso & grub-mk-rescue installed is used for compilation. An ISO will be generated at the end of the build process.
Git (Obviously) I don't think this needs an explaination.
VSCode (Optional, but highly recommended) Visual Studio code is our IDE of choice, and we have a number of recommended plugins.
- PowerShell Plugin by Microsoft This plugin gives you the ability to use the 'PowerShell' task type, allowing the automatic launching of virtualbox with the resulting image generated during compilation of Asuro.
VirtualBox Virtualbox is our Virtualisation environment of choice, don't ask why, it just is.

Installation (correct as of 2021/06/20)

Install WSL2 as described in the article linked above & ensure Virtualization is enabled in the BIOS.
Ensure WSL2 is used by default with the following command:
```
wsl --set-default-version 2
```
Install Docker for Windows.
Install Git for Windows.
Install VSCode & the listed plugins.
Install VirtualBox (v7+).
Clone this repository. The builder inherits the published Moderne/Pascal tooling image; see boot-unit generation.
Run the following command in the root of the repo to build the docker image:
```
docker compose build builder
```
Run the following command to compile Asuro:
```
docker compose run builder
```
Create a new virtual machine in Virtualbox and mount the Asuro.iso generated in step 9 as a boot image.
Add the virtualbox installation directory to your %PATH% environment variable, usually:
```
%PROGRAMFILES%\Oracle\VirtualBox
```
Naviage to your virtualbox machines folder, this is usually the following
```
%userprofile%\VirtualBox VMs\<VM Name>
```
Open the Virtual Machine Definition file (.vbox) in your text editor of choice and find the following line:
```
<Machine uuid="{7d395c96-891c-4139-b77d-9b6b144b0b93}" name="Asuro" OSType="Linux" snapshotFolder="Snapshots" lastStateChange="2021-06-20T20:33:07Z">
```
Copy the uuid, in our case 7d395c96-891c-4139-b77d-9b6b144b0b93 & create a localenv.json file in the project root with the following content:
```
{
    "VirtualBox":{
        "MachineName":"<YOUR_UUID_OR_MACHINE_NAME>"
    }
}
```
This will allow VSCode to automatically launch VirtualBox once Asuro has been compiled.

You can also enable the serial adapter "COM1" in mode "Raw File", give it a path, and provide this path in the localenv.json as follows:
```
{
    "VirtualBox" : {
        "MachineName": "<YOUR_UUID_OR_MACHINE_NAME>",
        "LogLocation": "Fully\\Qualified\\Path\\To\\Your\\Log\\File"
    }
}
```
This will allow you to see the console output from Asuro in your host terminal.
Open your project folder in VSCode, use CTRL+SHIFT+B to build & F5 to build + run in VBox.
Congratulations! You can now play with Asuro!

Notes & Gotchas

The above process has been updated to be compatible with VirtualBox 7+, in which VBoxSDL was removed and vboxmanage should be used in its place. A small wrapper powershell script is used to achieve this.
It was noted that Windows builds above 20H2 seem to have issues installing WSL2. We may have to wait for a patch from Microsoft to fix this. Our devs are currently using build 20H2.