Posts: 76
Threads: 2
Joined: May 2017
It seems there was a repo but they removed it:
https://aur.archlinux.org/cgit/aur.git/c...c6e4ffc639
Not a wise decision...
By the way I'm almost done. When deploying vapoursynth the user only needs to build the python module, vsscript and vspipe, which only requires python-dev to be installed and doesn't take much time. However I currently ran into an issue with running AppImages inside a chroot:
https://github.com/linuxdeploy/linuxdeploy/issues/86
Posts: 10.980
Threads: 57
Joined: May 2017
Nice. (shame about the repository,..)
I keep my fingers crossed that the AppImage bug will also be solved.
Cu Selur
Posts: 76
Threads: 2
Joined: May 2017
Updated the build files.
To build and deploy the tools run ./build-tools.sh and then ./deploy-tools.sh
To build and deploy VapourSynth including plugins run ./build-vapoursynth.sh, then ./build-plugins.sh and finally ./deploy-vapoursynth.sh
To install VapourSynth the user needs to install Python 3 development files (python3-dev on Ubuntu), extract vapoursynth_XXXXX.7z and run ./install-vs.sh.
It will copy the files into $HOME/opt, build the Python module, VSScript and vspipe (doesn't take much time) and create env.sh and vapoursynth.conf.
When I build on Ubuntu 16.04 and then install on Ubuntu 18.04 at least vspipe --version seems to work.
The mvtoolssf plugin by the way doesn't build on Ubuntu 16.04. It builds on Ubuntu 18.04 but even there it creates a lot of noise during the build.
Posts: 10.980
Threads: 57
Joined: May 2017
05.08.2019, 18:58
(This post was last modified: 05.08.2019, 20:16 by Selur.)
Quote:The mvtoolssf plugin by the way doesn't build on Ubuntu 16.04. It builds on Ubuntu 18.04 but even there it creates a lot of noise during the build.
I'll look into rewrite the scripts that instead of mvtools-sf it'll use mvtools.
Update: from the looks of it, it seems to be fine to simply use mvtools instead of mvtools-sf, since Hybrid doesn't really use it anyways.
-----------------
I ran:
- build-tools.sh and then deploy-tools.sh
it stopped with:
Quote:-- Deploying executables --
No such file or directory: ../Hybrid
(uploaded whole output to:
https://pastebin.com/ATqNFM1t)
the Hybrid was inside the Hybrid folder like the rest of the binaries
Cu Selur
Posts: 76
Threads: 2
Joined: May 2017
Strange, it's working fine for me. Make sure it's called "Hybrid" (case-sensitive) and it's inside the tools directory with the other binaries and it's not upx compressed.
Posts: 10.980
Threads: 57
Joined: May 2017
Hybrid is not compressed and inside the scripts/Hybrid folder like all the other tools, see:
https://pastebin.com/xQqW2Vyw
I still get: 'No such file or directory: ../Hybrid'
Cu Selur
Posts: 76
Threads: 2
Joined: May 2017
I can't reproduce your bug, sorry. I can only assume your deploy-tools.sh script isn't the same as mine.
My steps (inside Ubuntu 16.04 chroot; copying tools instead of rebuilding them from source):
git clone https://github.com/darealshinji/scripts
cd scripts/Hybrid/
cp -r ../../hybrid-tools/ tools
./deploy-tools.sh
hybrid is present and a regular binary file:
djcj ~/dev/scripts/Hybrid
$ file tools/Hybrid
tools/Hybrid: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/l, for GNU/Linux 2.6.32, BuildID[sha1]=07fee8cd17af233511b9d7de3850085315c29a6e, stripped
I see where the issue is: the tools must be inside a directory with the name "tools". I had changed that at some point.
Just download the latest scripts from Github and try it again:
https://github.com/darealshinji/scripts
Posts: 10.980
Threads: 57
Joined: May 2017
Quote: the tools must be inside a directory with the name "tools". I had changed that at some point
ahhh,... that was the issue I still had binaries inside the main folder and didn't see the tools folder.
-> okay 7z was created properly (would be better if it would be created next to the tools instead of inside the tools folder; nearly overlooked it
)
I then called ./build-vapoursynth.sh, but that stopped with:
This command is intended for maintainers to use
it deletes files that may require special tools to rebuild.
rm -f config.status config.cache config.log configure.lineno config.status.lineno
rm -rf ./autom4te.cache
rm -rf src/core/.deps src/cython/.deps src/filters/eedi3/.deps src/filters/imwri/.deps src/filters/misc/.deps src/filters/morpho/.deps src/filters/ocr/.deps src/filters/removegrain/.deps src/filters/subtext/.deps src/filters/vinverse/.deps src/filters/vivtc/.deps src/vspipe/.deps src/vsscript/.deps
rm -f Makefile
+ export PYTHONUSERBASE=/home/selur/workspace/scripts/Hybrid/build/FFmpeg/vapoursynth/temp
+ PYTHONUSERBASE=/home/selur/workspace/scripts/Hybrid/build/FFmpeg/vapoursynth/temp
+ pip3 install -q --user cython
Traceback (most recent call last):
File "/home/selur/opt/vapoursynth/bin/pip3", line 7, in <module>
from pip._internal import main
ImportError: No module named 'pip._internal'
see:
https://pastebin.com/Ak6akAMb
Cu Selur
Posts: 76
Threads: 2
Joined: May 2017
Of course I can change the script to save the 7z archive one directory above.
As for the build error: remove ~/opt/vapoursynth completely and try to build VS again. The issue seems to be a locally installed pip3 inside there, but there shouldn't be one.
Posts: 10.980
Threads: 57
Joined: May 2017
06.08.2019, 20:32
(This post was last modified: 06.08.2019, 20:34 by Selur.)
deleted ~/opt/vapoursynth and Hybrid/build then called ./build-vapoursynth.sh
-> no problem so far
Then I called build-plugins.sh and deploy-vapoursynth.sh which both completed without an error.
I then copied Hybrid_...7z and vapursynth_...7z to another VM, extracted them and called install-vs.sh
mkdir -p ~/opt && 7z x Hybrid_20190806.7z && mv hybrid ~/opt/
7z x vapoursynth_20190806.7z && cd vapoursynth_20190806 && ./install-vs.sh && cd .. && rm -rf vapoursynth_20190806
so far so good, now I will have to adjust Hybrid to the new location of files,... (and write new wrapper files to load the environment file)
-> will look into it over the weekend and report back
