-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[question] Why is --enable-cplugins not enabled by default? #4491
Comments
Not much. Mostly just being careful. I enabled it by default for now, but if there are any problems I might revert it. |
Awesome, thanks! When do you plan your next release? If it's still some time, it's not a problem at all. But if you're planning on doing a release soon anyway, I will not annoy my packager about this. |
Typically every 2-3 months, depends on @lachs0r. |
Got it. Thanks for the quick responses. |
11c7775 broke
|
@Safari77 highly doubt that's the fault of that commit, but rather, you updating waf. You should use the waf version that is specified in mpv, as different versions are incompatible with each other. |
I missed that waf 1.9.8 requirement. |
As of mpv 0.25.0, C plugin support must be enabled explicitly by setting
--enable-cplugins
at build time. What's the reason for this? I'm asking because I'd like to ask my distribution to ship mpv with plugin support enabled, but want to check first whether that's a safe thing for them to do.The text was updated successfully, but these errors were encountered: