I’ve had a few Emails recently about checking out the source for RISC OS from the ROOL CVS.
Here are the commands I used on a new Ubuntu installation to checkout the OMAP4Dev branch.

sudo apt-get install cvs
export CVSROOT=:pserver:anonymous:@riscosopen.org:/home/rool/cvsroot
cvs login
(if prompted for a password, just press return, no password is required)
cvs co -d bin castle/Admin/bin
chmod 0777 -R bin
sudo ln -s /usr/bin/perl /bin/perl
./bin/checkout OMAP4Dev

To checkout different branches of the CVS, simply change the last line, the current available options are;
BCM2835 – Raspberry Pi (Stable)
BCM2835Dev – Raspberry Pi (Dev)
BCM2835Pico – Raspberry Pi (Pico Dev)
Disc – Harddisc components (Stable)
DiscDev – Harddisc components (Dev)
iMx6Dev – ARMX6 (Dev)
IOMDHAL – Risc PC/A7000 (Stable)
IOMDHALDev – Risc PC/A700 (Dev)
OMAP3 – Beagleboard (Stable)
OMAP3Dev – Beagleboard (Dev)
OMAP4 – Pandaboard (Stable)
OMAP4Dev – Pandaboard (Dev)
OMAP5Dev – OMAP5 (Dev)
PlingSystem – !System components for pre RISC OS 5
Titanium – Titanium (Stable)
TitaniumDev – Titanium (Dev)
Tungsten – Iyonix (Stable)
TungstenDev – Iyonix (Dev)

This is a work in progress, and will be updated regularly.

Last Update: 16/04/2013
Document Version: 0.02

Software Required

RISC OS 4 or higher, though I’ve had issues using RISC OS 6
ROOL DDE – https://www.riscosopen.org/content/sales/dde
!UnTarBZ2 – https://www.riscosopen.org/tarballs/untarbz2.zip

Build Instructions

1. Download RISC OS source code for chosen hardware – https://www.riscosopen.org/content/downloads/risc-os-tarballs (Need Source Code Archives – Rebuilt Daily)

2. Make sure the !SetPaths application included with DDE tools has been ‘seen’ by the Filer

3. Extract the source code using !UnTarBZ2

4. Open the directory where the source code has been extracted

5. Open the folder name of platform. (OMAP3Dev, OMAP4Dev etc..) – This is referred to as the build directory.

6. Open the Prepare folder

7. Run the obey file !Run

8. In the task window, press ‘Y’ to answer each of the questions (3 Times)

9. !Builder should load automatically, menu click on !Builder and choose ‘register build tree’

10. Drag build directory into the window. (OMAP3Dev, OMAP4Dev etc..)

11. Click Save button

12. Select click on !Builder (On icon bar)

13. Ensure the correct build directory is selected (top option)

14. Select environment (ROOL.OMAP3, ROOL.OMAP4 etc..)

15. Select the build options – List, Clean, Clean all, Export headers, Export libraries, Export resources, make ROM, install ROM, Join ROM

16. Ensure Allignment Exceptions are turned OFF, and click the Build button

17. A task window is opened and the ROM image is built, takes approx 12 mins on PandaBoard-ES

18. Upon successful build a ROM image is placed in the Images folder.

19. Drink a beer 😀 (Or do this between 17 & 18!)

Todo

Add images
CVS Instructions
Youtube Video?
Document !UnTarBZ2 quirks (Random characters in filenames etc.)
DiscImage Building – Separate Guide?
Building with Allignment Exceptions turned on. (Chris Gransden’s Contributions)
Building on RISC OS 6

In an effort to keep up to date with the development over at www.riscosopen.org, I’ve setup some downloads of RISC OS 5 that are built from the cvs sources.

The plan is to update these regularly, and make them available to everyone, as the RISC OS Open boys don’t have time to keep rebuilding ROMS.

Next step is to automate the build process, and have new ROM images every day!

RISC OS ROM Images

As of today, I am the proud owner of an Iyonix computer. This is a very quick machine, quicker than the Beagle Board. (Or so it seems!)
This means I now own 13 machines capable of running RISC OS Plus I have my eye on machine number 14!