Can't compile on macOS (custom FFmpeg install causing issues?)
sinewave440hz opened this issue · 6 comments
Hi. I've previously had glslViewer up and running as per the macOS installation instructions. I've been using glslViewer daily up until the present issue. The issue began when I noticed that the record command wasn't working. Apparently I didn't have ffmpeg installed (or installed the same way, at least) last time I compiled glslViewer. Since then, I have begun to use ffmpeg extensively elsewhere and now have a custom-configured local installation that meets my needs and works well (elsewhere). However, when I try and re-compile glslViewer now, my make command fails with: ld: symbol(s) not found for architecture x86_64. After ruling out a few things, it seems that the problems here are due to the ffmpeg installation in some way. Can I use glslViewer with the latest ffmpeg installed locally?
Here is the cmake output:
cmakeoutput.txt
And the make output:
makeoutput.txt
Ffmpeg works fine in itself.
Unfortunately, after all this, I am getting the seg fault error and can't build to correct it. Is there a way to build without ffmpeg? Obviously it would be nice to have that in but it's more important to be able to use glslViewer at all...
UPDATE: I tried to compile after installing ffmpeg from Homebrew with the same result...so, some recent change in ffmpeg could be the cause. Still can't build though...
Well, I managed to run after installing glslviewer via homebrew instead. Same old problem with being unable to export video at all, but I suppose I can just screen capture the window and do whatever needs to be done separately in ffmpeg. Still, would have been nice though... :)
Hi! I'm sorry for this issue. Seams that is related to a regression on the code. I will try to give it a try on the next couple of weeks. Thanks for the heads up on it.
This is related to #322
Thanks @patriciogonzalezvivo. I'm relieved that I can use it in the meantime at least. Thanks for all your great work!
@sinewave440hz It's ok if I close this one? I will report progress on this other issue thread #322
Sounds like a plan! I didn't really recognise it as the same as #322, but I'm sure it's related if you think so :)