tl;dr: Anyone know how to add
ffmpeg to the CI tests or, better yet, as a build for a package?
I’m writing a package that relies on video IO. Since the VideoIO.jl package is not completely v1 ready (but in the process as much as I understand), I want to add
ffmpeg as a dependency to my package and then I just shell-out when video IO is needed in my package.
The ideal would be to get it as an actual build dependency. I think that might be too complicated for me (unless someone has already done this and has working code I can just copy-paste). Short of that, I’d love to at least add it to the tests on Travis and apveyor. I used to be able to do it with something like this. But that doesn’t work anymore (using the recommended travis and appveyor templates).
Any help appreciated!
EDIT: I don’t think we’ve made any progress recently, but I’ve got a few builder repos on my Github for dependencies which still are not building for some/many/most platforms. If we can get YasmBuilder working, it’ll make a lot of other things fall into place.
That said, I don’t know if anyone has started on the actual builder for ffmpeg itself, so if you feel like taking a shot at it, feel free. I’m sure many of us would be happy to help
Is there anything a monkey randomly typing on a keyboard can do?
ffmpeg in juliaobserver.com shows there are 11 packages that depend on
ffmpeg functionalities (e.g. Makie, VideoIO, Plots, Reel, EdgeCameras, etc), so I think solving this would be quite useful.
Well, the following worked out for me in the end, but only the CI way (so no build). Writing it down here, in case this proves useful to any future users:
- cinst ffmpeg
- if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then ./test/install_ffmpeg.sh ; fi
- if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then brew install ffmpeg; fi
sudo add-apt-repository -y ppa:mc3man/trusty-media
sudo apt-get -qq update
sudo apt-get install -y ffmpeg
install_ffmpeg.sh can be simplified.
Of course this is suboptimal – it allows for CI, but users will still need to manually install
ffmpeg on their systems for you package to work. The real work is the stuff mention above and worked on by @jpsamaroo and the good folks on that issue.