synapps-ioc

What problem does it solve?

It streamlines creating and configuring EPICS IOCs using the synApps xxx template, preventing common build failures caused by leftover artifacts, incorrect prefix/configuration, or missing module wiring.

Core Features & Use Cases

• Create IOC projects with mkioc: Generate a correctly-structured IOC from a chosen synApps version, including prefix renaming and RELEASE configuration.
• Ensure a clean build workflow: Make distclean before building to avoid incompatible pre-built objects inherited from the template copy.
• Configure IOC identity and startup safely: Edit settings.iocsh (e.g., PREFIX, ENGINEER, LOCATION) and use st.cmd.Linux includes (settings.iocsh, common.iocsh, then hardware .iocsh) in the correct order.
• Customize module linking via configure/RELEASE.local: Enable/disable synApps modules to control build time and IOC binary footprint, including platform-specific DBD selection.
• Add hardware using example iocsh includes: Copy example hardware configuration files into iocBoot and include them in st.cmd.Linux to load device databases and set up communication layers.

Quick Start

Tell the AI: Create a new synApps IOC named myioc using synApps 6-3 with prefix 32ida:, and include an example motors configuration in st.cmd.Linux, including the required make distclean before building.