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 2014-04-17 03:33:22 d45080306abe6c8190b85eb5c8cd794a	The complete RISC OS CVS repository as a compressed archive.	-	90.6 MB
	CVS (daily) 2014-03-11 02:31:05 9ab7874aca34a063401fb2b90e1aeda5	Changes to CVS repository over past 24 hours (rebuilt daily).	-	902.1 KB
	CVS (monthly) 2014-03-11 02:31:12 eeebec5e866fd81a6592b825138e2dda	Changes to CVS repository over past month (rebuilt daily).	-	19 MB
	CVS (weekly) 2014-03-11 02:31:06 c2be61f55abd5c54f8bf1e8f153b58df	Changes to CVS repository over past week (rebuilt daily).	-	2.5 MB

Source code archives (rebuilt daily) 

Icon	Name, date & MD5	Description	Version	Size	Details
	BCM2835Dev 2014-04-17 06:39:09 ef1740170f59ff4eac8bf68949f25bfa	Source code and build tree for the RaspberryPi development ROM. (Head revision. Work in progress.)	5.21	22.8 MB
	DiscDev 2014-04-17 06:38:48 851fe2edee6b6162aa42ac0ceb8845ed	Source code and build tree for the development disc image & boot sequence. (Head revision. Work in progress.)	5.21	27.1 MB
	IOMDHALDev 2014-04-17 06:38:15 fc0c7894b00272c5324074c2f8578540	Source code and build tree for the IOMD development ROM - A7000, RiscPC and RPCemu. (Head revision. Work in progress.)	5.21	21.6 MB
	OMAP3Dev 2014-04-17 06:38:25 46580fab7a644deb087b499f35ce3f37	Source code and build tree for the OMAP3 development ROM. (Head revision. Work in progress.)	5.21	21.7 MB
	OMAP4Dev 2014-04-17 06:38:59 d993d3c2999b8459cbc9908810533ad0	Source code and build tree for the OMAP4 development ROM. (Head revision. Work in progress.)	5.21	21.8 MB
	TungstenDev 2014-04-17 06:38:36 ddc15e23fffc6a6ef8e076d06efc1757	Source code and build tree for the Iyonix development ROM. (Head revision. Work in progress.)	5.21	23.1 MB

Other material

The gpl-build.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. It includes a binary copy of GCC 2.95.4 release 3, pre-installed into the build environment for your convenience. Since this is unmodified from the well-known RISC OS release, we are not including its sources. If you need them, you can get them from the riscos.info Subversion repository:

svn checkout svn://svn.riscos.info/gccsdk/tags/release_2_95_4_v3

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.