-
Notifications
You must be signed in to change notification settings - Fork 737
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build on Raspberry Pi 3 B+ fails on FFmpeg #545
Comments
@vb216 What would we need to support that model? |
@pwierzchon did it compile ok using Stretch distro on other Pi models / recently? Or has it never worked on Stretch? I'm guessing maybe different gcc version shipped nowadays, or one in the setup instructions isn't available any more (assuming its never worked on Stretch). Hopefully shouldn't be too tricky to resolve, will grab latest raspbian distro and give it a try locally. |
It compiled ok with Stretch distro 4-5 months ago. Now my company gave me a new Pi and asked me to set up the environment using new Stretch. |
pull #548 should fix this If you want it quickly, you can manually modify ./ffmpeg/cppbuild.sh to bring it in line - just needs an extra lib path added as I guess in latest Stretch they moved some things around |
Thanks @vb216! |
Great, FFmpeg passed.
|
Clue is in the message itself, you need to download flycapture (you have to accept some license stuff to be able to access it) and place it in ./javacpp-presets/downloads directory, then you can resume the build from that step, it'll find the flycapture source and carry on |
Right, just skip any module you don't need. BTW, the precompiled binaries
should work. Why not use those?
|
Hi, I want to compile javacpp-presets on Raspbery Pi 3 B+ with the new Raspbian Stretch. I follow your instructions which worked perfectly for build on the previous RPi model (https://github.com/bytedeco/javacpp-presets/wiki/Build-Environments), but this time it fails on FFmpeg giving the following stack trace:
Any ideas how to fix that?
The text was updated successfully, but these errors were encountered: