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 2019-04-23 03:35:07 e070ca3901ac3873026309e757221c02 | The complete RISC OS CVS repository as a compressed archive. | - | 131.4 MB |  |
| CVS (daily) 2019-04-23 06:05:59 dc3c5b7343467141544cdbe61d406d54 | Changes to CVS repository over past 24 hours (rebuilt daily). | - | 412.6 KB | |
| CVS (monthly) 2019-04-23 06:06:20 c213f80ab7e287738e12468f7ed4d2cb | Changes to CVS repository over past month (rebuilt daily). | - | 6 MB | |
| CVS (weekly) 2019-04-23 06:06:05 b3b03bbc0e125124319d22391db0443a | Changes to CVS repository over past week (rebuilt daily). | - | 676.1 KB | |
Source code archives (rebuilt daily)
| Icon | Name, date & MD5 | Description | Version | Size | Details |
|---|---|---|---|---|---|
| BCM2835Dev 2019-04-23 06:03:42 e323b88054e9520f4f4c109f6fc37a14 | Source code and build tree for the RaspberryPi development ROM. (Head revision. Work in progress.) | 5.27 | 22.9 MB | |
| DiscDev 2019-04-23 06:04:31 1ade923279852def9576f13e5529471c | Source code and build tree for the development disc image & boot sequence. (Head revision. Work in progress.) | 5.27 | 29 MB | |
| IOMDHALDev 2019-04-23 06:00:23 6d45d0d654cfef7ff76d37595142a0fa | Source code and build tree for the IOMD development ROM - A7000, RiscPC and RPCemu. (Head revision. Work in progress.) | 5.27 | 21.8 MB | |
| OMAP3Dev 2019-04-23 06:01:43 a5e2f16d193f11e11bd26dc0c8ab01f8 | Source code and build tree for the OMAP3 development ROM. (Head revision. Work in progress.) | 5.27 | 22.1 MB | |
| OMAP4Dev 2019-04-23 06:02:22 7f11e300cd3e604b82868142d7d32182 | Source code and build tree for the OMAP4 development ROM. (Head revision. Work in progress.) | 5.27 | 22.1 MB | |
| OMAP5Dev 2019-04-23 06:03:02 c7234c328bcf97eaad6d78c48125308b | Source code and build tree for the OMAP5 development ROM. (Head revision. Work in progress.) | 5.27 | 22.2 MB | |
| TitaniumDev 2019-04-23 06:05:09 93492366cb56467ae24f2ca8fd1cb876 | Source code and build tree for the Titanium development ROM. (Head revision. Work in progress.) | 5.27 | 22.1 MB | |
| TungstenDev 2019-04-23 06:01:03 f4ae0756251d57cee3916d25419b00c4 | Source code and build tree for the Iyonix development ROM. (Head revision. Work in progress.) | 5.27 | 23.2 MB | |
| iMx6Dev 2019-04-23 06:05:52 d776dc2326b55369df68d7f553b0b911 | Source code and build tree for the Wandboard development ROM. (Head revision. Work in progress.) | 5.27 | 24.9 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.
