[vlc-devel] Project of generation libvlc.lib compatible with MS Visual Studio.

Jacques Boileau jboileau at gmail.com
Thu Nov 10 18:28:18 CET 2011

Hi Remi,

I do not imply that Videolan should deliver any part of VisualStudio
to end users. Just that it is probably needed when Videolan would
generate the .lib to be included in the package. Since most Videolan
developers are Linux developers, whoever does the builds may not have
access to Microsoft stuf.

And no VisualStudio, or even lib.exe from it, is an included component
of Windows.

Jacques Boileau

2011/11/10 Rémi Denis-Courmont <remi at remlab.net>:
> Le jeudi 10 novembre 2011 19:05:29 Jacques Boileau, vous avez écrit :
>> How to implement this in the make whoever is beyond my knowledge of
>> make files. But we would need to have access to lib.exe from
>> VisualStudio, so the build configuration would have to know where it
>> is. I know most of you are Linux oriented developers so I don't know
>> if you have VisualStudio available when you do your Win32
>> build.
> VisualStudio is not a component of the Windows operating system, or is it?
> | "(...) as a special exception, the source code distributed need not
> | include anything that is normally distributed (in either source or
> | binary form) with the major components (compiler, kernel, and so on)
> | of the operating system on which the executable runs, unless that
> | component itself accompanies the executable."
> I'd strongly advise not to VisualStudio (or any other proprietary tools chain)
> with (L)GPL derived work unless your competent lawyer told you it's OK.
> The .lib file really should be generated by binutils if it is useful.
> --
> Rémi Denis-Courmont
> http://www.remlab.net/
> http://fi.linkedin.com/in/remidenis
> _______________________________________________
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
> http://mailman.videolan.org/listinfo/vlc-devel

More information about the vlc-devel mailing list