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 am trying to test everparse and, as I am working on MacOS and am not expecting to modify the code, I am trying to use the Docker image.
First of all, in the documentation, it is stated that Those Docker images include a fully built and tested EverParse in the quackyducky subdirectory which is not correct as there is no quackyducky folder. I think that everything is in the everparse folder instead.
Then, there is no everparse.sh as stated, so I tried qd.exe in ever parse/bin which does not seem to be an executable of everparse. After some digging, I understood that I should use the 3d.exe executable instead but when I tried, it failed because of the missing environment variables.
I am currently writing a new Dockerfile with trial and error method.
I wanted to let you know that the documentation is outdated (or incorrect but more probably just outdated :) )
Thanks!
The text was updated successfully, but these errors were encountered:
Hi!
I am trying to test everparse and, as I am working on MacOS and am not expecting to modify the code, I am trying to use the Docker image.
First of all, in the documentation, it is stated that
Those Docker images include a fully built and tested EverParse in the quackyducky subdirectory
which is not correct as there is noquackyducky
folder. I think that everything is in theeverparse
folder instead.Then, there is no
everparse.sh
as stated, so I triedqd.exe
inever parse/bin
which does not seem to be an executable of everparse. After some digging, I understood that I should use the3d.exe
executable instead but when I tried, it failed because of the missing environment variables.I am currently writing a new
Dockerfile
with trial and error method.I wanted to let you know that the documentation is outdated (or incorrect but more probably just outdated :) )
Thanks!
The text was updated successfully, but these errors were encountered: