-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] fzn-choco.exe doesn't work #1097
Comments
I have no doubt that the script can be improved in many ways. |
Hello But Nuitka makes possible to turn a Python app into an executable. I suggest using the Python script instead of the bash script. This lets you run choco-solver with MiniZinc options outside MiniZincIDE. You can also integrate the executable you create with Nuitka directly into MiniZincIDE. |
I pushed some changes. |
Thank you, I'll test it when I have time. |
I tested the script and I have two comments:
and passing this bat script to minizinc works. Maybe it should be added somewhere in the docs. |
It seems a simpler alternative to maintain. fzn-choco.sh#!/bin/bash
# Call the python script with the arguments passed to this script
python3 fzn-choco.py "$@" fzn-choco.bat@echo off
:: Call the python script with the arguments passed to this script
set "PY=%~dp0fzn-choco.py"
python3 %PY% %* and update the documentation and remove the |
Describe the bug
I tried adding Choco to MiniZinc IDE on Windows and encountered several problems with
fzn-choco.exe
script:.exe
extension it's actually a bat script, so the execution fails.The syntax of the command is incorrect.
. And even if it's fixed, there also is a logical error in the parsing, it considers path to flatzinc file as unrecognized argument.I'm not sure if the script is just wrong or some problems are caused by my Windows installation,
To Reproduce
Try adding Choco to MiniZinc on Windows.
Expected behavior
Everything should work.
Possible solution
I managed to make it work with trial and error. It's quite ugly and I'm not sure I found every possible bug, but I can make a pull request if you want.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: