How to build latest versions

[jr-peterzon]

The recent changes have changed the way things are built.
Perhaps we can have a wiki page on how to build from source?
Also it seems that the build script from the Multithreading branch requires something like INTS setup. No idea what it should be.

Previous builds could be done using:

./build -DSINGLE_CORE -Wno-unused-const-variable -Wno-unused-function -DDEBUG__SHOW_MODULE_INIT

But that will stop already with an error:

Please locate a RiscOS build tree (or a symbolic link to one) as RiscOS

So we probably need to install a RiscOS build tree. Would we be able to just do a checkout in some way?
Do we need the RISC OS Compiler suite to compile it (like we do with RISC OS on Linux)?

I really hope to follow the development by doing builds and simple tests.
Best regards,
Jan Rinze.

[Simon-Willcocks]

It's not that easy, I'm afraid. The modified code needs to be built on RISC OS, as far as I know, and my attempts to create a patch file are running into difficulties.

Can you build ROM images on Linux? If so, where's that described?

[janrinze]

the project RISCOS on Linux does build the ROM from Linux. it uses a RISCOS rom as bootstrap to run the DDE tools for building the ROM. Depending on the platform it runs it in QEMU or native.
it has a requirement that the DDE tools are in a specific directory next to the RISCOS on Linux directory.

[janrinze]

The https://github.com/TimothyEBaldwin/RISC_OS_Linux_Source has a README that says:
ACORN_CPP : Path to AcornC.C++ directory of DDE, default is ../DDE/AcornC.C++

on most ARM platforms the build is pretty straight forward.

[Simon-Willcocks]

So it has to be an ARM Linux?

I want to post a patch file, but I'm having difficulties with diff and file types.

What I did manage, when I was on holiday and hadn't access to my RO machine, was to improvise builds with an existing ROM image and hal.script. Unfortunately, I've managed to break something that OS_Heap doesn't even work in the boot code. I'll try and fix it.

[Simon-Willcocks]

I tried a build on Linux on a Pi, but the build fails with undeclared name __schedule_barrier, maybe my DDE is too old?

[janrinze]

Yes.. unfortunately your DDE is too old.
When I had that issue I bought a newer version from ROOL.
About building on non ARM platforms, that should be possible since RISC OS on Linux can use qemu for the build.

[Simon-Willcocks]

It only seems to be used in the HAL, which I don't need...

Anyway, I worked out what I did wrong. Regardless, if you unzip the attached and delete the part of the build script that created hal.script, this might let you build something not very useful.

workaround.zip

[Simon-Willcocks]

Apologies, I'm really not trying to waste your time!

Here's another workaround, but it only works with the Multithreading branch. I'll upload that shortly after I've posted this, so I can include the URL of the zip file
workaround2.zip
.

[Simon-Willcocks]

Ignore the link in the git commit log, use the one from the main page. I just tried this and it "worked".

wget https://github.com/Simon-Willcocks/RISC-OS-Kernel-in-C/archive/refs/heads/Multithreading.zip &&
wget https://github.com/Simon-Willcocks/RISC-OS-Kernel-in-C/files/9096026/workaround2.zip &&
unzip Multithreading.zip &&
cd RISC-OS-Kernel-in-C-Multithreading/ &&
unzip ../workaround2.zip &&
./build -DSINGLE_CORE && qemu-system-arm -bios latest.bin -machine raspi2 -serial stdio | grep 'Scan keyboard with timeout' -m 10 -B 100000 | tee /tmp/log

[janrinze]

only change i needed to do is -B armv7 into -B arm to get it to build.
Looks nice!
I tried the mouse input but i think it's too early for that, right?

[Simon-Willcocks]

I'll leave it to you to work out why all the font text is in the same place and the wrong size! :)

Yes, I've just done timer interrupts so far, but there's a solid foundation, I hope.

Did you look at the cross-compiler-with-riscos-newlib directory? It's early days, but I hope it will allow applications to be written using gcc with minimal effort to move on to newer versions.