Skip to content

Compatibility and support

The native C++ package targets Windows x64 and Linux x86_64. It provides the runtime, MCP server, browser application, semantic catalogues, and built-in domain plugins.

What is included

The native packages provide:

  • project creation and inspection;
  • metadata, operation-graph, cache, and audit operations;
  • catalogue-backed MCP Operations and operation-graph schemas;
  • mass-spectrometry analysis, spectrum, and chromatogram access;
  • native readers for supported mzML and vendor-container formats.

Support varies by backend, domain, file format, and platform. Vendor-reader availability should be confirmed for the specific format and dataset.

Runtime requirements

Keep the package's catalogue files with the executable. Optional scientific tools such as Open Babel, Java, and MetFrag are separate dependencies and are not automatically installed by the native packages.

Interface selection

  • Use the C++ package for native C++ applications or the C++ MCP server.
  • Use the R package for R and Shiny workflows.

The native packages do not promise a stable cross-version C++ ABI. Match an application or plugin developer kit to the runtime version it targets.

Reporting a compatibility issue

When a file or workflow does not behave as expected, record the streamfind version, operating system, operation name, relevant parameters, and a minimal reproducible project or data description. Keep vendor-format support claims specific to the tested file family and acquisition mode.

Release validation

The native 0.7.1 release is intended to be validated on both supported package platforms. From the repository root, use the platform release scripts so that the frontend, native runtime, CTest suite, package contents, dependency closure, and packaged MCP interface are checked together:

scripts\release\cpp\release-cpp.ps1

On Linux, run:

scripts/release/cpp/release-cpp-linux.sh

The release validation must report the complete CTest suite passing and successful packaged MCP smoke validation. The resulting archives and sha256sums.txt are written to tmp/release-output/ and should be checked before publishing them.