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