[vlc-devel] [PATCH v2 13/13] extras: extract the contrib sources before building them

Steve Lhomme robux4 at ycbcr.xyz
Fri Jul 10 16:10:42 CEST 2020

On 2020-07-10 15:02, Alexandre Janniaux wrote:
> Hi,
> On Fri, Jul 10, 2020 at 01:08:40PM +0200, Steve Lhomme wrote:
>> On 2020-07-10 12:26, Alexandre Janniaux wrote:
>>> Hi,
>>> On Fri, Jul 10, 2020 at 11:30:38AM +0200, Steve Lhomme wrote:
>>>> On 2020-07-10 11:06, Alexandre Janniaux wrote:
>>>>> Hi,
>>>>> The point of Remi, that I agree on, is that you're not
>>>>> supposed to follow contrib build lines, or you're supposed
>>>> First time I hear that logs should not be read. If that's the case we can
>>>> redirect them to /dev/null
>>> Read doesn't mean follow. You can easily spot which contrib failed
>>> and just run the build of the very contrib that failed.
>> No I can't *just* run the build. I have nothing to compile for macOS or iOS.
>> I need to be able to read the logs when there's something wrong.
> I compile both on my Linux machine, although macOS is still
> a bit unconvenient to compile. But if you don't want to fiddle
> about the setup, then in this very case it is mainly an issue
> within the CI, not an issue with the contribs.
> Even with changing the CI build script, if the contrib cannot
> be tested for all platform at once, it should probably be
> enabled only for the platform you can test, and then enabled
> platform by platform by other developers who can test on their
> side and be able to actually test the end result.
> CI resources are quite scarce and expensive so using them to
> develop is slow, inefficient resource-wise and has an impact
> on other developer's build which are only validation.

If this is the case we should not move to Gitlab. All code that will be 
merged will have to pass those CI's before being merged.

More information about the vlc-devel mailing list