Closed sjorspeterse closed 3 years ago
Both of the dependencies of vega-cli (yarn and node) are already on conda-forge, so adding Windows support simply consists of replicating the build.sh
script in a bld.bat
file. I took a first stab at it, but I run into some issues. yarn add
installs the vega-cli package successfully, and when executing the vg2pdf.cmd
and other commands (which are just a wrapper for invoking node vg2pdf
as Windows does not recognize shebangs) from the $PREFIX/lib/vega-cli/node_modules/.bin/
folder they fork file. However if I make a symlink of them to the $PREFIX/bin
folder they stop working as node.exe
looks for the vg2pdf
script in the wrong palce.
I can see two solutions:
vg2pdf.cmd
during build to have it point to the right folder. It is not very appealing as that file is created (downloaded?) by yarn, and I feel that it should not be messed with.But I'm a bit ahead of myself. First, and most importantly, are you devs even open to adding Windows support to this feedstock? If yes, then what do you think about the above solutions? Or is there a proper way to symlink the yarn-created .cmd file to a directory on the path, that I am missing?
Issue: No Windows support
Hi! I'm trying to get altair_saver to work, but it depends on this package. Are there any plans on supporting Windows?
Environment (
conda list
):Details about
conda
and system (conda info
):