-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Better solution for graphviz executable #34
Comments
Just to propose a solution here, would it be possible to add a hard link to executables in |
@ccordoba12, as you are pretty familiar with this problem, do you have any thoughts on this? |
The right solution would be to compile Graphviz on Windows, but that seems pretty hard. The problem with the current approach is that the Graphviz installer that we're repackaging as a conda package comes with a lot of third-party libraries (like Qt4 and zlib), so we need to put its contents on So I think the batch script approach is the right one for now (I can't think of a better one). We just need to submit patches to the upstream projects that depend on Graphviz to make them work with batch scripts. That's usually a matter of adding |
I discovered a tough limitation with BAT files: they don't work with UNC |
No, thanks. |
Note that |
So that sounds like a |
Thank you, i reported it in conda-forge/python-graphviz-feedstock#32 as advised. I wanted to cast here my -1 vote against batch proxies for the forthcoming 2.40 release. |
sphinx doesn't generate inheritance graphs, if I understand correctly it's because it doesn't support the batch script. Adding |
We are now building from source on Windows with PR ( #59 ) 😀 |
Currently the
graphviz.exe
file is installed inLibrary\bin\graphviz
. This causes some complications when people want to call the executable as that is not added to the path. Currently we address that by creating a batch script inLibrary\bin
, which calls the executable inLibrary\bin\graphviz
. This causes issues downstream where we have needed to extra work to call the batch script. Am wondering if there is a better way for us to address this, which would result in less downstream pain.xref: conda-forge/python-graphviz-feedstock#6
xref: ContinuumIO/anaconda-issues#1666
The text was updated successfully, but these errors were encountered: