Selur's Little Message Board
[GUIDE] Ubuntu repository - maintained by djcj - Printable Version

+- Selur's Little Message Board (https://forum.selur.net)
+-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html)
+--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html)
+--- Thread: [GUIDE] Ubuntu repository - maintained by djcj (/thread-18.html)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

RE: Ubuntu repository - maintained by djcj - Selur - 13.07.2019

Okay, Ubuntu 19.04 required:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
for the 32bit binaries to work. (Man, not the best error message to indicate that i386 libraries are missing. :/)

Cu Selur

Ps.: now, I see your posts about it. Wink

RE: Ubuntu repository - maintained by djcj - Selur - 13.07.2019

About Vapoursynth:
I'm not sure installing it to ~/vapoursynth is such a good idea.
I guess for both the Hybrid and Vapoursynth a 'good' location should be /opt/hybrid and /opt/vapoursynth. What do you think?
(or /usr/share/hybrid and /usr/share/vapoursynth or ~/bin/hybrid and ~/bin/vapoursynth)

Small correction:
shouldn't be:
git clone --depth=1 https://github.com/Selur/VapoursynthScriptsInHybrid vsfilters
but
git clone --depth=1 https://github.com/Selur/VapoursynthScriptsInHybrid vsscripts

Cu Selur

RE: Ubuntu repository - maintained by djcj - djcj - 13.07.2019

About the compression thing... you can simply change the script to use the directory name "hybrid" instead of "deploy" and just add the compression command at the end.
Modify the script to your needs.

By the way I hope you're not planning to use Ubuntu 19.04 as your default build system, because that would mean most of the binaries you build will not work on older Ubuntu versions. You should better keep 16.04 as your build system. In fact, the linuxdeploy guys even recommend using Ubuntu 14.04.

RE: Ubuntu repository - maintained by djcj - Selur - 13.07.2019

I plan to stick with 16.04 as build system until the LTS maintenance support runs out (iirc April 2021).
I just used 19.04 since I haven't used it and new users might potentially use it.
I mainly dropped 14.04 because of the lack of Qt5. Wink

Cu Selur

RE: Ubuntu repository - maintained by djcj - Selur - 14.07.2019

ARGH,... sadly it seems like at least
export PYTHONPATH="/home/selur/bin/vapoursynth/lib/python3.7/site-packages:$PYTHONPATH"
needs to be in the global environment.

Adjusting the process environment to:
QT_ACCESSIBILITY=1
  LANG=de_DE.UTF-8
  LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
  GTK_IM_MODULE=ibus
  GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
  SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
  IM_CONFIG_PHASE=2
  DESKTOP_SESSION=ubuntu
  GTK_MODULES=gail:atk-bridge
  SHLVL=1
  SHELL=/bin/bash
  XAUTHORITY=/run/user/1000/gdm/Xauthority
  XDG_SESSION_ID=2
  XDG_CURRENT_DESKTOP=ubuntu:GNOME
  GDMSESSION=ubuntu
  PYTHONPATH=/home/selur/bin/vapoursynth/lib/python3.7/site-packages;
  GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/31ccec33_12aa_425c_b57c_e2404407180b
  XDG_MENU_PREFIX=gnome-
  QT4_IM_MODULE=xim
  _=./bin/hybrid/Hybrid
  LESSCLOSE=/usr/bin/lesspipe %s %s
  TERM=xterm-256color
  XDG_SESSION_CLASS=user
  GNOME_TERMINAL_SERVICE=:1.109
  QT_MAC_DISABLE_FOREGROUND_APPLICATION_TRANSFORM=1
  GJS_DEBUG_TOPICS=JS ERROR;JS LOG
  SSH_AGENT_PID=1542
  LOGNAME=selur
  WINDOWPATH=2
  PWD=/home/selur
  QT_IM_MODULE=ibus
  XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg
  XDG_SESSION_TYPE=x11
  LESSOPEN=| /usr/bin/lesspipe %s
  DISPLAY=:0
  XDG_DATA_DIRS=/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop
  COLORTERM=truecolor
  XDG_SESSION_DESKTOP=ubuntu
  XDG_VTNR=2
  LD_LIBRARY_PATH=/home/selur/bin/vapoursynth/lib;
  HOME=/home/selur
  DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
  OLDPWD=/home/selur/bin/vapoursynth
  CLUTTER_IM_MODULE=xim
  USERNAME=selur
  SESSION_MANAGER=local/selur-VirtualBox:@/tmp/.ICE-unix/1396,unix/selur-VirtualBox:/tmp/.ICE-unix/1396
  XDG_RUNTIME_DIR=/run/user/1000
  XMODIFIERS=@im=ibus
  VTE_VERSION=5602
  GJS_DEBUG_OUTPUT=stderr
  GNOME_DESKTOP_SESSION_ID=this-is-deprecated
  PATH=/home/selur/bin/hybrid;/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
  XDG_SEAT=seat0
  GNOME_SHELL_SESSION_MODE=ubuntu
  USER=selur
isn't enough. (adding ' export PATH="/home/selur/bin/vapoursynth/bin:$PATH" ' isn't necessary)
Starting vsViewer while PYTHONPATH is only set in the process environment of vsViewer results in 'Failed to initialize VapourSynth' when trying to start the preview. :/

Cu Selur

RE: Ubuntu repository - maintained by djcj - djcj - 14.07.2019

If there's no other way you could rename vsViewer to vsViewer.real and create a shell script with the name vsViewer that sets PYTHONPATH and launches vsViewer.real.
I can also change the build script to use program checkinstall to install vapoursynth globally.

RE: Ubuntu repository - maintained by djcj - Selur - 14.07.2019

I'll play around with the idea, not sure whether this would cause other problems,..

RE: Ubuntu repository - maintained by djcj - Selur - 14.07.2019

Okay, seems to work, but I'm struggling with linux shell syntax:
I thought that (vsViewer_withenv.sh):
#!/bin/bash
scriptDir=$(dirname -- "$(readlink -f -- "$BASH_SOURCE")")
env="$HOME/bin/vapoursynth/env.sh"

if [ -f "$env" ]
then
  echo "sourcing $env"
  source "$env"
else
  echo "'$env' does not exist!"
fi
vsViewer="$scriptDir/vsViewer"
sh -c "exec $vsViewer $@"
would work and it does as long as there are no parameter to vsViewer.
Problem is when I use, for example
"/home/selur/bin/hybrid/vsViewer_withenv.sh" --preview-only "/home/selur/Schreibtisch/HybridTemp/tempPreviewVapoursynthFile10_53_36_442.vpy" --aspect 1 --matrix Rec709 --crop off#0#0#0#0
I get a 'File open error':
Quote:failed to open the file --preview-only

Seems like the exec call at the end of the vsViewer_withenv.sh script is not totally correct. :/
Any idea how this should look to work properly?

=> think I got it with
exec -l "$vsViewer" "$@"

Cu Selur

RE: Ubuntu repository - maintained by djcj - Selur - 14.07.2019

Would be nice if:
a. the build-vapoursynth-ubuntu.sh will also create an executable 'vspipe_withenv.sh' next to vspipe with the following content:
#!/bin/bash
scriptDir=$(dirname -- "$(readlink -f -- "$BASH_SOURCE")")
source "$scriptDir/../env.sh"
vsPipe="$scriptDir/vspipe"
exec -l "$vsPipe" "$@"

b. if build-vapoursynth-ubuntu.sh instead of installing vapoursynth to '$HOME/vapoursynth' would install to '$HOME/vapoursynth/bin' by default.

c. the 'deploy.sh' script would also create a 'vsViewer_withenv.sh' next to vsViewer with the following content:
#!/bin/bash
scriptDir=$(dirname -- "$(readlink -f -- "$BASH_SOURCE")")
env="$HOME/bin/vapoursynth/env.sh"

if [ -f "$env" ]
then
  echo "sourcing $env"
  source "$env"
else
  echo "'$env' does not exist!"
fi
vsViewer="$scriptDir/vsViewer"
exec -l "$vsViewer" "$@"

Okay, so the general calling of vsViewer seems to work, problem now is the compilation&deployment of the Vapoursynth filters.
Do you have a build script for the filters?

Cu Selur

Ps.: uploaded a package to https://selur.net/dev/linux/Hybrid_20190714.7z (includes vsViewer_withenv.sh and has an adjusted Hybrid which looks for vsViewer_withenv.sh next to the vsViewer binary and for vspipe_withenv.sh next to vspipe, both try to source ~/bin/vapoursynth/env.sh)

RE: Ubuntu repository - maintained by djcj - djcj - 14.07.2019

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:
#!/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.