[vlc-devel] [RFC] Plugins linking

[Laurent Aimar]

Hi,

On Fri, Feb 13, 2009, Rémi Denis-Courmont wrote:
> There has been much trolling (especially from my own self) on the linking
> of VLC plugins against the VLC core since I changed to try to fix static
> builds a while ago. I would euphemistically say that this was probably not
> the brightest idea of mine.
> 
> Not linking the plugins against libvlccore:
> [...]
> - prevents missing symbols detection at build-time of plugins,
> - does not work on Windows (hence a special hack for Windows currently).
[1]
> 
> Including the VCS revision information:
> [...]
> - forces a relink of anything that links against libvlccore at every make
> invocation.
[2]

 From what I understand of the issue:
 - if [1] cannot be fixed cleanly/in a portable way, then linking again against
 libvlccore has to be done. I don't think there is a lot to argue in this case.
 - [2] is a stopper for any developper at least if it is the default behviour.

 So I think that we should link against libvlccore and disable VCS revision
information (to avoid [2]).

 I don't think any body would be against a solution to enable VCS revision
information based on a configure.ac option if possible. But as long as
no one propose a clean patch to do this, VCS revision information should be
disabled.

Regards,

-- 
fenrir