14.07.2019, 16:14
Why not use "$HOME/.hybrid/vapoursynth" for the VS installation? I have "$HOME/bin" added to PATH and I try to avoid installing directories in there.
The following script works for me:
Running ./Hybrid/vsViewer_withenv.sh --preview-only filedoesntexist.vpy gives me an error about "filedoesntexist.vpy" being missing and not "--preview-only".
By the way, now that I think about it I remember that you cannot set LD_LIBRARY_PATH in C/C++ using setenv() and then excpet the exec() functions to use that new path. But I can set a RUNPATH for the installed libraries, maybe that way vsViewer runs VS properly by only setting the PYTHONPATH.
The following script works for me:
#!/bin/sh
scriptDir="$(dirname "$(readlink -f "$0")")"
env="$HOME/.hybrid/vapoursynth/env.sh"
if [ -f "$env" ]; then
echo "sourcing $env"
. "$env"
else
echo "'$env' does not exist!"
fi
"$scriptDir/vsViewer" $*
Running ./Hybrid/vsViewer_withenv.sh --preview-only filedoesntexist.vpy gives me an error about "filedoesntexist.vpy" being missing and not "--preview-only".
By the way, now that I think about it I remember that you cannot set LD_LIBRARY_PATH in C/C++ using setenv() and then excpet the exec() functions to use that new path. But I can set a RUNPATH for the installed libraries, maybe that way vsViewer runs VS properly by only setting the PYTHONPATH.