Skip to content
Coordinator DB
View as Markdown
View as Markdown

Validate a macOS cross build ​

A build produced on another host needs runtime evidence from its intended macOS target. Producing a file alone does not establish that the executable starts, finds its configuration or completes a query there. This guide defines verification evidence; the installation page remains the reference for the current installation procedure.

Identify both environments ​

Record the build host separately from the target Mac, including the target architecture and macOS version. State whether verification used a physical Mac or another execution environment. Preserve that distinction in a report instead of describing all macOS targets as tested.

Exercise the target executable ​

Copy the intended executable with the supplied config.xml and users.xml into a test directory on the target. Start it there and check the native interface:

sh
./coordinator serve --config-file config.xml --db cross-check.db
sh
./coordinator client --database data --query "SELECT 1 FORMAT csv"

Expect one row containing 1. Test file input and output formats used by the application after this smoke check. If execution fails before SQL runs, capture the launch error and target details. Do not infer database behavior from a loader or permissions failure; see local verification.