RISC OS source code

RISC OS sources are available from CVS or you can download our source code archives on this page. If you download anything, please consider donating to help support the ongoing shared source project. Thanks!

Source code summary

You can either download an archive as a raw CVS repository (requiring a CVS server to manipulate them) or a complete source tree including build environment for the build you are interested in.

CVS repository archives (rebuilt daily) 

Icon	Name, date & MD5	Description	Version	Size	Details
	CVS 2018-04-24 03:34:30 efa9e45153d74b54bb3fc7c38c9477cc	The complete RISC OS CVS repository as a compressed archive.	-	129.7 MB
	CVS (daily) 2018-04-24 08:32:45 f8bb1bc40645eea9385c82a3e9a0bfb4	Changes to CVS repository over past 24 hours (rebuilt daily).	-	63.5 KB
	CVS (monthly) 2018-04-24 08:32:48 7a17b224d090d661408309e0efd7b3c5	Changes to CVS repository over past month (rebuilt daily).	-	5.8 MB
	CVS (weekly) 2018-04-24 08:32:46 0e97533c077dfe5bf3593fe1169651c3	Changes to CVS repository over past week (rebuilt daily).	-	2.7 MB

Source code archives (rebuilt daily) 

Icon	Name, date & MD5	Description	Version	Size	Details
	BCM2835Dev 2018-04-24 08:32:29 477409a9fc9b1c3c349d6fb4c6f7f518	Source code and build tree for the RaspberryPi development ROM. (Head revision. Work in progress.)	5.25	22.7 MB
	DiscDev 2018-04-24 08:32:35 5b221db9316d16830882eae58f0f38bb	Source code and build tree for the development disc image & boot sequence. (Head revision. Work in progress.)	5.25	27.9 MB
	IOMDHALDev 2018-04-24 08:32:11 bc984450095d0afeeefa3b8666b41797	Source code and build tree for the IOMD development ROM - A7000, RiscPC and RPCemu. (Head revision. Work in progress.)	5.25	21.6 MB
	OMAP3Dev 2018-04-24 08:32:20 43ebcb6c95578f5bb942c0da589060d7	Source code and build tree for the OMAP3 development ROM. (Head revision. Work in progress.)	5.25	21.9 MB
	OMAP4Dev 2018-04-24 08:32:25 e270fb6f4c81511820d2e5e1a94b96c0	Source code and build tree for the OMAP4 development ROM. (Head revision. Work in progress.)	5.25	21.9 MB
	TitaniumDev 2018-04-24 08:32:39 33f130592955f82dcc4f58f497318948	Source code and build tree for the Titanium development ROM. (Head revision. Work in progress.)	5.25	22 MB
	TungstenDev 2018-04-24 08:32:16 69bd94efc40621dc6c38aeae02525e87	Source code and build tree for the Iyonix development ROM. (Head revision. Work in progress.)	5.25	23 MB
	iMx6Dev 2018-04-24 08:32:45 e086ba430d2dc77358e7c2f2353bd715	Source code and build tree for the Wandboard development ROM. (Head revision. Work in progress.)	5.25	24.6 MB

Other material

The gccsdk-gcc-src-4.7.4-Rel3.tar.bz2 file is only required if you want to rebuild from source the GPL-licenced tools which are used by the main build process, and can be used either by itself or merged in with the other tarballs. There’s a binary copy gccsdk-riscos-tools-src-4.7.4-Rel3.zip of GCC 4.7.4 release 3 available as well, though the subset of tools required are already included in the Library directory of each of the source code archives.

Unpacking

You should unpack any zipfile download, those which end in “.zip”, using SparkFS, SparkPlug or a similar unzipping program – see our additional instructions below. Any downloads which are supplied as a (compressed) tarball, those which end in “.tar” or “.tar.bz2”, should be unpacked using our UnTarBZ2 application, which can be downloaded here. This application includes a Help file so you should be able to refer to that for further instructions.

Ensure you unpack the archive contents onto a filesystem that supports long filenames and more than 77 files per directory!

Viewing

The RISC OS sources are written in a mixture of languages, including C, ARM assembler and even BBC BASIC. For RISC OS desktop users, there are a number
of editors which are capable of viewing this source code including Zap and StrongEd. For Windows users, it may be hard to find editors which provide
syntax colouring for ARM assembler. To help you to read these sources, you can use the freeware ROView program, illustrated here. It’s not an editor,
but it is a configurable ARM assembler source code viewer with syntax colouring.

Building

To build the sources, download the source code archive(s) you are interested in. You will need to add in your C toolset and the C library using script included in the build environment (RiscOS.Library.InstallTools). For more information, please see the detailed Wiki page which describes the process in full. It may also help to understand the directory structure inside some of the tarballs if you read about the CVS repository layout too.

SparkFS

With the kind permission of David Pilling, RISC OS Open supply a self-extracting (on RISC OS) read-only version of the SparkFS application. This can be downloaded here – just set the filetype to Utility and then run it to extract the application. For more information about this application, and to purchase the read/write version, see the SparkFS pages here.

A note for SparkFS users

If using SparkFS to read the Tar files, you need to configure it to give unknown filetype files RISC OS filetype &fff (Text) rather than its default of &ffd (Data). It is a good idea to set its filename truncation value to a high number so that it doesn’t accidentally shorten any filenames, too. From the command line, issue the following commands before opening your Tar archive:

*SparkFSExtension fff
*SparkFSTruncate 255

With these commands issued, SparkFS should extract the archive contents correctly. Note that while the *SparkFSTruncate command can be added to !SparkFS.!Run – indeed, it seems that some versions of SparkFS have this included by default – the *SparkFSExtension fff command only works if issued after SparkFS has started. To work around the problem, modify file !SparkFS.CONFIG.Extensions instead of using the command. Change the first line to read, simply:

0xfff

This should have the same effect as *SparkFSExtension but will be set up by default when SparkFS starts.