This page aims to be a step-by-step guide to help people who are unfamiliar with the ROM build system to build their first ROM image.
RISC OS uses ROM images that are customised to different machine types. Use the table below to work out which “product” you need to use to build a ROM that’s suitable for a particular machine.
|Product||Builds a ROM suitable for…|
|IOMD||RiscPC, A7000, RPCEmu|
|OMAP3||BeagleBoard, ARMini and other OMAP3-based machines|
|OMAP4||PandaBoard, ARMiniX and other OMAP4-based machines|
|Titanium||RapidO-Ti, TiMachine and other Titanium-based machines|
There is also a “Disc” product, for building the base hard disc image; see the notes at the bottom of this page for the extra steps necessary to build that.
cvs -z9. See here for more info about the .cvsrc file.
rsync -a —exclude=CVS/ —exclude=.cvstag * .
OS developers will often want to customise the ROM images they build, e.g. to enable debug output for particular modules, or to enable the debug serial terminal. Customising the ROM in this way is somewhat beyond the scope of this document, so please take any questions you have to the forums.
Building the disc image differs from building a ROM image in two ways:
Note also that the disc image is created as a set of separate files, which should be installed by copying them to a blank hard disc/SD card under RISC OS. Additional tools are required if you want to create an image file which can be written to a disc by ‘dd’, Win32DiskImager, etc.
See here for information about the best practices to follow when dealing with CVS directly.
Get in touch with ROOL, they can provide CVS write access to those who need it. See the remote write access to the ROOL CVS repository page for further details.