Rapid SCADA: Selecting and Building Source Versions

The master and develop source distributions do not, by themselves, identify a specific Rapid SCADA version in the available evidence. When reproducibility matters, select the required source version from the project's releases rather than assuming either branch represents a known release.

Select a Defined Source Version

Use the Rapid SCADA releases area to obtain the source for a specific version. Record the selected release with the build artifacts so another engineer can rebuild the same source instead of relying on the changing master or develop distribution.

Build the Required Solutions in Order

Build the documented solutions in this exact sequence:

Log
Report
ScadaData
ScadaComm
OpenKPs
ScadaServer
ScadaAdmin
ScadaWeb
ScadaScheme

The source tree contains additional solutions, but the evidence does not define dependencies or an internal order for them. Build those solutions only after completing the listed sequence.

Treat DLL Compatibility as Unverified

Do not assume the GitHub DLL directory is identical or compatible across every source version. The available evidence gives no version-to-DLL compatibility matrix. Keep DLL files aligned with the selected source release and treat any cross-version reuse as a hypothesis that requires a clean build and functional verification.

Verify the Build

Confirm that every solution in the required sequence builds successfully before compiling the remaining solutions. If a build fails, first verify that the source and DLL files came from the same selected release, then identify the first failing solution in the prescribed order; later failures may be downstream effects.

FAQ