-
Notifications
You must be signed in to change notification settings - Fork 266
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
FFmpeg won't compile #622
Comments
Yes, you can't use schannel, openssl, or gnutls with each other. They're all implementations of TLS. |
d2fbc6d should fix it. |
logs.zip
|
That's an FFmpeg issue, ask them. |
I wonder if it's related to ffmpeg changing some variables eg from ff_ to av_ OTOH, I use gnutls and my build process, which I ran just now, works ok, so who knows. edit no, discount the above rubbush after all. |
Reported in ffmpeg trac as ticket #6801. Reply from heleppkes:
|
Surprising for me, the ffmpeg options set file "ffmpeg_options.txt" (I selected ffmpegChoice=1) contains the Zeranoe compatible option "--enable-gnutls". |
I think the default "ffmpeg_options.txt" created by MABS needs to be changed. Here's the configuration for Zeranoe's ffmpeg builds. It includes "--enable-gnutls" but not "--enable-openssl" (which makes sense because they're incompatible). So "--enable-openssl" shouldn't be included in the "# Zeranoe" section. I also recommend adding a comment that openssl and gnutls are incompatible, so only one should be enabled. I also compared MABS' options for a Zeranoe-style build and noticed a lot of differences.
Options included in Zeranoe but not in MABS:
So I'm curious what all these differences mean - especially the options included in Zeranoe's build but not in MABS', and if MABS could add more functionality to its ffmpeg build by including them. |
Most of those are auto-enabled by default. libsnappy is in the zeranoe-like list, last I saw. libxml2 is a recent addition. gmp is used if gcrypt isn't and schannel or gnutls are enabled. libshine looks to be a fixed-point mp3 encoder, useless nowadays imo. |
Whoops, you're right about "--enable-libsnappy" being in MABS' Zeranoe-like list. "--enable-gpl" is as well (I edited my previous post to reflect that).
Since I'm assuming the vast majority of MABS users are compiling ffmpeg for personal use, they'd want the opposite of that (i.e., including "--enable-gpl" and "--enable-nonfree") so that they could include any external libraries they want. However, according to ffmpeg's wiki That implies to me that you wouldn't want GPL enabled since it isn't compatible with some libraries such as libfdk_aac. But then later in that wiki entry it says that compiling ffmpeg with libfdk_aac
So apparently you can compile ffmpeg with libfdk_aac while GPL is enabled (even though they aren't compatible) as long as you also include "--enable-nonfree"... Clearly I don't understand the licensing details, but based on all the above information, am I correct in assuming that the best configuration for a personal build of ffmpeg that can use any library would include "--enable-gpl" and "--enable-nonfree"? Are "--enable-d3d11va" "--enable-dxva2" and "--enable-nvenc" auto-enabled by MABS? |
Just run ffmpegs ./configure --help and check the output for [autodetect] ... |
[everything regarding licenses] |
@schmidthubert I can view and edit the "configure" file in "/build/ffmpeg-git" but I can't figure out how to actually run the script. However I did use PowerShell to run "ffmpeg -buildconf" and got this output
Out of the 12 options included in Zeranoe's configuration but not listed in MABS' "ffmpeg_options.txt" |
@wiiaboo Got it - thanks for clearing that up. |
See my reply in this question as well ... At the end you'll have to ask yourself "what do I need", "what does NOT work" etc before you blow up your binary with functions you never need ... |
You shouldn't do that, that's exactly what the suite is for ... |
And don't use Powershell to run configure. There is a mingw64.exe in msys64 folder to open a shell, for instance ... Then cd to the build/ffmpeg-git folder ... |
@schmidthubert you said
What I meant by my response was that I didn't know how to do that, even though I know where the configure file is. I didn't use Powershell to run the configure file, I used it to run ffmpeg's buildconf option. I tried to run ./configure --help using msys2.exe before and it didn't work. After reading your reply, I used mingw64.exe and got it to work. I see a long list of options, but how am I supposed to know what components/external libraries are/aren't included in my ffmpeg build based on options that say [autodetect] in their descriptions? |
You know what IS included by running "ffmpeg -h full > help.txt" and then read the file, then you know what's included. Did you even try running ffmpeg -h (without full switch) at all and READ the output to start with? |
Yes, I did run ffmpeg -h and I did READ the output. Did you even READ my earlier posts? How do you think I got all the information I included? What I've been trying to figure out is if all the options included in Zeranoe's configuration are also in MABS' configuration, even if they're not specifically listed. I figured out by running ffmpeg -hwaccels that [in my build at least] d3d11va and dxva2 are. But I still don't know about a lot of the others like zlib for example. And it's not exactly like the full help printout is very helpful. Mine's 10,410 lines long, and searching for zlib didn't find any results. But for all I know, maybe its functions/components are in my ffmpeg build. If I knew all the ins and outs of ffmpeg and everything related to building it, I wouldn't need MABS and wouldn't be asking questions about it here. |
All these questions are irrelevant. The only relevant question is does the program work for you or not. If not go to the ffmpeg users list and ask there for help ... |
logs.zip
I'm getting the following error when trying to compile a full build of FFmpeg:
ERROR: schannel requested, but some conflicting dependencies are unsatisfied: openssl gnutls
From what I can tell, openssl and gnutls seem to serve the same function. Could the issue be that FFmpeg can only be compiled with one - not both - of them? But if that's the case I don't understand why it's just now failing to compile since I haven't changed any options.
The text was updated successfully, but these errors were encountered: