[vlc-devel] [PATCH] configure: remove the CONFIGURE_LINE from the config.h
remi at remlab.net
Thu Jan 30 08:49:34 CET 2020
I believe that the official Debian build rules fail if a flag is skipped, but that's not the point anyway.
If you don't look at bug reports, you should not be making this kind of comments. And if you did look at them, you would know that VLC 4 debug logs show used modules just like they always did. What they don't show and never showed are the modules that were not successfully probed.
Le 30 janvier 2020 09:02:14 GMT+02:00, Steve Lhomme <robux4 at ycbcr.xyz> a écrit :
>On 2020-01-29 17:46, Rémi Denis-Courmont wrote:
>> Le keskiviikkona 29. tammikuuta 2020, 11.31.47 EET Marvin Scholz a
>>> only the things that were explicitly specified, so it is
>>> nearly always useless…
>> Which is actually very useful to know what was explicitly enabled and
>> disabled. Especially if the packaging rule dutifully sets all
>> Debian does.
>So if one doesn't dutifully enable/disable new modules we added (in 4.0
>for example) there is no way to tell from this string if it's enabled
>Also on my Debian, there are many extra vlc packages for specific
>modules like "vlc-plugin-fluidsynth", "vlc-plugin-samba",
>"vlc-plugin-bittorrent", etc. I assume the string doesn't tell you VLC
>was compiled with those, nor if it's installed or not.
>> It's not as good as a list of available modules, but for lack
>> still much better than *nothing*.
>It's informational at best and can't be used to actually find out what
>module is used and why. I don't know if anyone pays attention to it, I
>know I haven't.
>Also given we don't even have a way to list the used modules anymore I
>suppose that's something we don't care about anymore.
>vlc-devel mailing list
>To unsubscribe or modify your subscription options:
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vlc-devel