[vlc-devel] [RFC] Merging extras/tools & contribs

Steve Lhomme robux4 at ycbcr.xyz
Mon Feb 11 16:45:39 CET 2019

On 11/02/2019 09:10, Rémi Denis-Courmont wrote:
> Hi,
> The thing is, the Win32Compile wiki page still advises using prebuilt 
> contribs. I don't think GPL is a problem on Windows desktop. That 
> being the case, I don't thini we can break prebuilt contribs...

I've used this page a lot but now it's outdated. I have my own guide to 
build VLC on Msys2: https://github.com/robUx4/vlc-msys

The prebuilt never worked out of the box due to some symbolic link not 
extracting properly with tar. One has to copy files manually and run the 
prefix "fix" as well. So I doubt anyone is using it.

> (It might be a problem for proprietary LibVLC apps, but regardless of 
> prebuilt contribs.)
> Le 11 février 2019 08:48:58 GMT+02:00, Steve Lhomme <robux4 at ycbcr.xyz> 
> a écrit :
>     On 09/02/2019 10:53, Rémi Denis-Courmont wrote:
>         Le lauantaina 9. helmikuuta 2019, 9.48.32 EET Steve Lhomme a
>         écrit :
>                 In principles, you *can* compile native code within
>                 contribs. This is what the luac target does due to
>                 hysterical raisins. There may be regressions, if some
>                 cross-compilation variable values are leaked by an
>                 export or such. Normally, they should only be set with
>                 HOSTVARS or HOSTVARS_PIC, as this advises (for> xFLAGS
>                 variables): | # Do not export those! Use HOSTVARS.
>                 Regardless, building native executables in contribs is
>                 rather nasty. The resulting (pre-built) contrib would
>                 depend on a specific build environment, which it
>                 really should not. 
>             I thought prebuilt was dead, at least for license reasons. 
>         Uh, please clarify. I don't understand how licensing could
>         affect prebuilt VLC contribs any more or less than built VLC
>         releases. 
>     I can't find the thread in my emails so maybe it was on IRC or IRL. But
>     the general idea was that if we build all contribs, even GPL ones, some
>     people might end up building/distributing VLC with these without
>     realizing it.
>     Aside from that, unless the contribs are built with the same toolchain,
>     especially regarding C++, there's a high chance the prebuilt package
>     will not work for most people. Let alone the protoc compatibility gamble.
>     prebuilt saved my life so many times in the past when the contribs
>     wouldn't build properly with msys2+mingw64 but now all this is solved.
>     So at least on Windows people should not use that anymore (for the
>     reasons stated above) and I don't know if contribs make sense elsewhere,
>     maybe macOS ?
>     ------------------------------------------------------------------------
>     vlc-devel mailing list
>     To unsubscribe or modify your subscription options:
>     https://mailman.videolan.org/listinfo/vlc-devel
> -- 
> Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez 
> excuser ma brièveté.
> _______________________________________________
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
> https://mailman.videolan.org/listinfo/vlc-devel

More information about the vlc-devel mailing list