RISC OS source code

RISC OS sources are available from Git or you can download our source code archives below. If you download anything, please consider donating to help support the ongoing open source project. Thanks!

Source code archives (rebuilt daily) 

Icon	Name, date & MD5	Description	Version	Size	Details
	BCM2835Dev 2025-04-28 00:28:53 0f8791789f4234690eff1d81ebc5177b	Source code and build tree for the Raspberry Pi development ROM. (Head revision. Work in progress.)	5.31	23.2 MB
	DiscDev 2025-04-28 00:29:02 9c4d519fb4e0d76b9eb58eb09ffdd2ef	Source code and build tree for the development disc image & boot sequence. (Head revision. Work in progress.)	5.31	31.3 MB
	IOMDHALDev 2025-04-28 00:28:35 54a62eeac6e85f4a61e2334f9b168ab7	Source code and build tree for the A7000, A7000+, and RiscPC development ROM. (Head revision. Work in progress.)	5.31	22.2 MB
	OMAP3Dev 2025-04-28 00:28:42 1409fc31587a9fd0dba6063fdb91ca58	Source code and build tree for the OMAP3 development ROM. (Head revision. Work in progress.)	5.31	22.2 MB
	OMAP4Dev 2025-04-28 00:28:46 9555d938b815aaad4196a4047a430a3f	Source code and build tree for the OMAP4 development ROM. (Head revision. Work in progress.)	5.31	22.2 MB
	OMAP5Dev 2025-04-28 00:28:50 1d86b5044d3c81744cb5932e1e9f51ec	Source code and build tree for the OMAP5 development ROM. (Head revision. Work in progress.)	5.31	22.5 MB
	PineA64Dev 2025-04-28 00:28:58 54924f32917210cf8edacfa106c19a92	Source code and build tree for the Pinebook development ROM. (Head revision. Work in progress.)	5.31	47.5 MB
	TitaniumDev 2025-04-28 00:29:06 7f8f4878c1693001d7a8e17415cb4d87	Source code and build tree for the Titanium development ROM. (Head revision. Work in progress.)	5.31	22.4 MB
	TungstenDev 2025-04-28 00:28:39 6f2530173c399b98eca0297c03f54a45	Source code and build tree for the Iyonix development ROM. (Head revision. Work in progress.)	5.31	23.4 MB
	iMX6Dev 2025-04-28 00:29:10 11e8f0b3b76cfc578f7fa9038fd73fb0	Source code and build tree for the Wandboard development ROM. (Head revision. Work in progress.)	5.31	25.3 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 BBCBASIC. For RISC OS desktop users, there are a number of editors which are capable of viewing this source code including SrcEdit, StrongEd and Zap.

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 a script included in the build environment (RiscOS.Library.InstallTools). For more information, please see the detailed Wiki page which describes the process in full.

SparkFS

With the kind permission of David Pilling, RISC OS Open supply a self-extracting (on RISC OS) version of the SparkFS application. This can be downloaded here – just set the filetype to Utility and then run it to extract the application.

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.