Skip to content

Select the matching installed solver in mzn-gecode launchers - #264

Merged
zayenz merged 2 commits into
mainfrom
feature/6.5.0-mzn-launcher-selection
Oct 22, 2026
Merged

zayenz merged 2 commits into
mainfrom
feature/6.5.0-mzn-launcher-selection

Conversation

@zayenz

@zayenz zayenz commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

Current MiniZinc does not use the launcher's FLATZINC_CMD selection, and adding the Gecode library with -I can leave MiniZinc's bundled solver library selected. Both launchers now select the installed gecode.msc, which identifies the matching executable and library. The Unix fallback for older mzn-fzn installations is retained.

Extend the existing installed-tools smoke check to compile and solve a MiniZinc model using gecode_gcd. Install the official MiniZinc 2.10.1 Linux bundle in the job that runs this check, verifying its published SHA-256. Only MiniZinc 2.10 is tested.

Validation: the installed launcher compiled and solved the model with MiniZinc 2.10.1 from an installation prefix containing spaces; the previous launcher failed this check. The Linux archive checksum and layout, workflow YAML, shell syntax, source tidiness, and generated-source freshness checks passed. The Windows batch launcher was not executed locally.

@zayenz
zayenz force-pushed the feature/6.5.0-mzn-launcher-selection branch from e4f30ae to 529e885 Compare October 22, 2026 12:04
@zayenz
zayenz merged commit c1ec25b into main Oct 22, 2026
16 checks passed
@zayenz
zayenz deleted the feature/6.5.0-mzn-launcher-selection branch October 22, 2026 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant