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 2019-07-16 06:34:38 b022ebc7a4ea884eb20d27dd30da83f2	Source code and build tree for the RaspberryPi development ROM. (Head revision. Work in progress.)	5.27	22.7 MB
	DiscDev 2019-07-16 06:35:25 5f39cd08635c024e069dfbf87d7b605f	Source code and build tree for the development disc image & boot sequence. (Head revision. Work in progress.)	5.27	28.7 MB
	IOMDHALDev 2019-07-16 06:31:36 fbe46cba8d1a978ab9f4820693eb2b2a	Source code and build tree for the IOMD development ROM - A7000, RiscPC and RPCemu. (Head revision. Work in progress.)	5.27	21.7 MB
	OMAP3Dev 2019-07-16 06:32:48 2f457ab50ecf956432dab80cc22e61de	Source code and build tree for the OMAP3 development ROM. (Head revision. Work in progress.)	5.27	21.8 MB
	OMAP4Dev 2019-07-16 06:33:25 df260aed1e8f18936ffe4b3eeb890641	Source code and build tree for the OMAP4 development ROM. (Head revision. Work in progress.)	5.27	21.9 MB
	OMAP5Dev 2019-07-16 06:34:02 cdb9c5841caf1603b6bfd4123a8ac356	Source code and build tree for the OMAP5 development ROM. (Head revision. Work in progress.)	5.27	22 MB
	TitaniumDev 2019-07-16 06:36:01 1281698ffd566687630672a7b1ff14fd	Source code and build tree for the Titanium development ROM. (Head revision. Work in progress.)	5.27	21.9 MB
	TungstenDev 2019-07-16 06:32:13 49c945c876af1ff99ce8c696e4cb41e9	Source code and build tree for the Iyonix development ROM. (Head revision. Work in progress.)	5.27	22.9 MB
	iMx6Dev 2019-07-16 06:36:44 de01f3223eb18c2aac545ddf0f84de3f	Source code and build tree for the Wandboard development ROM. (Head revision. Work in progress.)	5.27	24.8 MB

Ungrouped 

Icon	Name, date & MD5	Description	Version	Size	Details
	Cvs Repos 2019-07-16 03:35:15 e070ca3901ac3873026309e757221c02	-	-	131.4 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 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.