Introduction and Overview
Part 2 is the main workflow guide for day-to-day use of the build environment. It explains how to work inside the container, how projects are laid out and maintained, how builds and remote runs fit together, and how to look up or author documentation as part of normal development.
Read this part in order if you are new to the environment. Once you know the overall workflow, use the chapter summaries below to jump straight to the task you are about to perform.
Chapters
Shell and host integration
Use Shell and host integration when you need to understand how the container shell maps your checkout, which host bridge commands are available, and how to move simple file-opening or editing tasks back to the host system.
Files, directories, and variables
Use Files, directories, and variables for the standard directory mappings, the host variables that influence startup, and the ways to pass extra directories or variables into the environment.
Project creation and management
Use Project creation and management for skeleton creation, version-file workflows, project-administration helpers, and the normal lifecycle for a new native RISC OS project.
Porting existing C projects
Use Porting existing C projects when you are adapting an existing POSIX-style source tree to the RISC OS build model rather than starting a fresh native project layout.
Building, linking, and outputs
Use Building, linking, and outputs for the shared AMU makefile system, the normal build entry points, output directory conventions, and the occasions when direct compiler or linker use is useful.
Generated build assets
Use Generated build assets for module header generation with CMunge, generating language headers from assembler definitions, and building or inspecting ALF libraries.
Packaging and source maintenance
Use Packaging and source maintenance for packaging built output as ZIP, Spark, ArcFS, or TBAFS archives, and for checking or formatting C sources with riscos-cppcheck and riscos-indent.
Testing and running
Use Testing and running for remote execution with riscos-build-run, return-file workflows, and the boundary between remote testing and the optional local runtime support described later in the manual.
Documentation lookup and inspection
Use Documentation lookup and inspection for environment help, PRM lookups, library and header symbol searches, and the built manual opened through riscos-help.
Documentation authoring and manual building
Use Documentation authoring and manual building for PRM-in-XML authoring, interface-generation workflows that produce help or headers, and the build steps for standalone and indexed manuals.