[vlc-devel] [PATCH 00/14] Move VLM implementation to a module

[Jean-Baptiste Kempf]

On Wed, 16 Sep 2020, at 17:07, Rémi Denis-Courmont wrote:
> Le keskiviikkona 16. syyskuuta 2020, 11.23.50 EEST Romain Vimont a écrit :
> > Hi Rémi,
> > 
> > On Tue, Sep 15, 2020 at 09:10:16PM +0300, Rémi Denis-Courmont wrote:
> > > Le tiistaina 15. syyskuuta 2020, 20.37.32 EEST Romain Vimont a écrit :
> > > > This removes a lot of VLM code (including parsing) from libvlccore.
> > > 
> > > What is the actual point of this?
> > 
> > The idea was to lighten and simplify libvlc core (the complexity being
> > moved to the VLM module), and not load the VLM code in memory when VLM
> > is not used (which is often the case).
> 
> If you want to de-bloat libvlccore, move the gcrypt-based update code to a 
> module. With static linking that's orders of magnitude larger than any other 
> core component.

Yes, and the changes around gcrypt were blocked by your objections, in a similar way that this current discussion.

> Moving code to a module marginally increases disk and memory use due to module 
> overhead. If the module is not used, it might marginally decrease memory use, 
> but probably won't. And even if it does, it's a coin toss whether it'll 
> actually offset the increase.

It's also to load less parsing-code by default.

-- 
Jean-Baptiste Kempf -  President
+33 672 704 734