-
Notifications
You must be signed in to change notification settings - Fork 76
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
[Windows x64] Fails to export images #28
Comments
There is a bug in GR 0.18.0. We are working on version 0.19.0, which will be built using MingW64 on Windows. This will solve the problem ... |
Thank you for your quick answer! Would you have an expected date for GR 0.19? I cannot see anything on your website… |
I hope we can deploy 0.19.0 next week ... |
@dourouc05 : Did 0.19.1 solve your problem? |
Sorry for the delay. No, the update did not solve this issue: just making a Then, I tried to
(If I try directly through GR or through a layer like Plots, I get the same result.)
If I can do other tests to help you understand what's happening, please ask! |
Actually, I think the issue is worse than that: on a headless server (Linux, RHEL 7.2), I get a very similar error message. With the same script as before:
The Julia version is slightly older (it would be possible to update it, but I'm not root on that machine).
Or is this issue completely different from the previous one? (It seems GR is looking for something around OpenGL? Is a X server absolutely required, even if I don't draw anything on the screen? That would sound strange… and indicate there is a missing test when installing GR.jl.) |
GR requires a default Desktop environment which should contain the package We could catch that condition thus disabling all GR3 functionality and accelerated output in GR, e.g. |
@dourouc05 : On my Windows 10 VM, I had to remove temporary files and folders (using the system tools) to get the correct binaries installed in the |
I tried reinstalling GR.jl after cleaning everything I could (with the Disk Clean-up tool, also for system files), but it did not change the result. To make sure this is the problem, I downloaded by hand the GR binaries (http://gr-framework.org/downloads/gr-0.19.1-Windows-x86_64.tar.gz) and installed them in GR (after deleting the deps/gr and deps/downloads folders)… and the result is still the same. I could not find a GR function (in the C API) that returns the version: that would be an easy check to ensure the downloaded version is the expected one (even though it seems there is something for the Python module). |
@dourouc05 : Ok, please download http://gr-framework.org/downloads/gr-latest-Windows-x86_64.tar.gz. I should have mentioned that I used the GR master branch. Sorry for the inconvenience ... |
No problem, it's really nice that you spend time to help me, thank you! There is a change in error message with those new binaries (still in a popup):
It's much less scary, but I'm still clueless about how to export PNGs. |
@dourouc05 : We obviously have a problem with our build system. I'll check (and test) this before making more recommendations ... :-) |
Latest gr binaries seem to work on Windows! 🎉 |
@pfitzseb : So you were faster than me making an announcement. But I had to apply another patch fixing a problem with filenames containing multiple periods, which caused |
Great! Thanks for fixing that :) |
The precompiled master branch also works on my side! Thanks for your support! |
On Windows, when trying to export simple plots, I get the following error message:
I use the following script to trigger the error:
With a Plots.jl script, the same error appears:
However, both perfectly show a window with the plot in it.
I guess something went wrong with the installation of GR. I use version 0.13.0, installed directly with
Pkg.install("GR")
; Julia is 0.4.6, x64, on Windows 10 x64. I have a fileC:\Users\Thibaut\.julia\v0.4\GR\deps\gr\gsplugin.dll
, so it seems it is not missing.Looking with Dependency Walker (http://www.dependencywalker.com/) at that file, it looks like it's missing a file:
gsdll64.dll
. It looks like Ghostscript, so I downloaded it (http://ghostscript.com/download/gsdnld.html) and put the corresponding DLL in the same folder. For Dependency Walker, everything looks OK… but I still get the same error!Is there any missing dependency hidden somewhere? Or a bug of another kind?
The text was updated successfully, but these errors were encountered: