You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to try viasp with one of my encodings inside a bigger project structure
where the encoding is split up in modules and I am using #include statements to put them together.
This seems to give an error with the relative imports as the encoding is not in the same directory as from where I am running.
The viasp.log is full of these errors
<string>:1:1-28: error: file could not be opened:
base/defined.lp
<string>:3:1-30: error: file could not be opened:
base/structure.lp
<string>:4:1-29: error: file could not be opened:
base/discrete.lp
<string>:5:1-35: error: file could not be opened:
base/clingo/integer.lp
<string>:7:1-35: error: file could not be opened:
base/clingo/boolean.lp
etc...
The text was updated successfully, but these errors were encountered:
Thank you for reporting this. This is a duplicate of #92. This is fixed on the dev branch and will be included in the next release. For now, I recommend cloning the repo and installing the dev branch, or comment out include statements and mention the input files in the viasp command.
I wanted to try viasp with one of my encodings inside a bigger project structure
where the encoding is split up in modules and I am using
#include
statements to put them together.This seems to give an error with the relative imports as the encoding is not in the same directory as from where I am running.
The
viasp.log
is full of these errorsThe text was updated successfully, but these errors were encountered: