RISC OS  OPEN

CVS repository guide

While RISC OS was still owned and being developed by Acorn Computers, it existed under a number of different source control systems. Towards the end of the 1990s, it was migrated into a single CVS (concurrent versioning system) repository. This allowed multiple users to access and modify sources and to both keep the older revisions as well as a history of what the changes to each source file were.

Since that time, the RISC OS repository has continued to be used by Castle Technology and includes all of the sources required to build the ROM image for an IYONIX PC computer, as well as for the IYONIX disc build.

This document aims to give a quick overview of what lives where in the RISC OS CVS repository as well as a bit of information about each component you’ll find in there.

For more information on the use of CVS, products files and the custom tools for RISC OS, you should read the “Using the RISC OS repository” document. To find out more about how to actually build RISC OS components from their sources, you should read the How to Build RISC OS document.

Overview

/Admin       \
/bin          } these directories are used by cvs and include some custom
/CVSROOT     /  tools for managing the repository

/Products    - contains various products files. These are lists of
               components and their corresponding CVS tag (version) so that
               a complete product can be checked out of CVS (e.g. sources
               for a ROM build)

/bsd         - sources published under a BSD-style license
/castle      - all of the RISC OS sources published under the Castle
               Technology license live within here
/gpl         - sources published under a GPL license
/other       - any sources which are published under some other license

More Detail

The /castle directory contains various subdirectories, as follows:

/RiscOS/Apps               - applications used during the build process
/RiscOS/BuildSys           - various files required for multi-component
                             builds
/RiscOS/Env                - obey files to set up environment variables for
                             a given build
/RiscOS/Export             - all exported headers go into the Export
                             directory
/RiscOS/Install            - the built software for disc-loading ends up
                             in here
/RiscOS/Images             - ROM images are built into here
/RiscOS/Library            - all of the build tools live in here (see note)
/RiscOS/Sources            - the main body of the RISC OS sources live
                             within here...

/RiscOS/Sources/Apps       - sources to various applications (e.g. Paint)
/RiscOS/Sources/Audio      - all audio-related components
/RiscOS/Sources/Desktop    - things relating to the window manager (Wimp)
/RiscOS/Sources/FileSys    - file system components
/RiscOS/Sources/HAL        - hardware abstraction layer sources
/RiscOS/Sources/HWSupport  - low-level hardware drivers and related tools
/RiscOS/Sources/Internat   - message files, internationalisation, etc.
/RiscOS/Sources/Kernel     - the RISC OS Kernel sources
/RiscOS/Sources/Lib        - libraries such as TCP/IP and SharedCLibrary
/RiscOS/Sources/Networking - networking modules and other components
/RiscOS/Sources/OSVersion  - required for giving ROM builds a version
/RiscOS/Sources/Printing   - all of the printing stack
/RiscOS/Sources/Programmer - many components related to programming/debug
/RiscOS/Sources/SystemRes  - resources, e.g. System, Configure, Scrap
/RiscOS/Sources/Toolbox    - all of the toolbox modules and libraries
/RiscOS/Sources/Utilities  - various utilities, e.g. HForm, SaveCMOS
/RiscOS/Sources/Video      - display stuff, e.g. font manager, draw module

/RiscOS/Utilities          - the sources to some additional utilities

The /RiscOS/Library directory contains many binaries which are needed to do a build. However, you also require the Acorn C/C++ tools suite in order to build almost any component. This is because the Acorn C/C++ tools includes the C compiler, the ARM assembler and the linker (amongst other things).

If you have the suite installed, an obey file within /RiscOS/Library can be run to ensure that the tools are installed into /RiscOS/Library from your Acorn C/C++ installation.