[vlc-devel] [PATCH 3.0 01/17] contrib: clean dependency on win32 pthread

[Hugo Beauzée-Luyssen]

On Mon, Mar 30, 2020, at 9:44 AM, Steve Lhomme wrote:
> On 2020-03-27 18:13, Hugo Beauzée-Luyssen wrote:
> > On Fri, Mar 27, 2020, at 4:57 PM, Steve Lhomme wrote:
> >> and define the macros to force using the static version
> >>
> >> (cherry picked from commit f52ef651974696f59261d699241d622e323a32df)
> >> ---
> >>   contrib/src/aom/rules.mak        |  9 ++++++++-
> >>   contrib/src/libplacebo/rules.mak |  6 +++++-
> >>   contrib/src/mysofa/rules.mak     | 11 +++++++++--
> >>   contrib/src/openjpeg/rules.mak   | 10 +++++++++-
> >>   contrib/src/protobuf/rules.mak   |  9 ++++++++-
> >>   contrib/src/srt/rules.mak        |  2 ++
> >>   contrib/src/vpx/rules.mak        |  6 +++++-
> >>   contrib/src/zvbi/rules.mak       |  5 +----
> >>   8 files changed, 47 insertions(+), 11 deletions(-)
> >> >> ...
> >>   
> >>   .zvbi: zvbi
> >>   	$(UPDATE_AUTOCONFIG)
> > 
> > No objection with the set, but could you send it through the CI to be sure?
> 
> I tried the 4.0 one on Gitlab but it assumes some files present in 
> extras/ci which are not found in 3.0. Do we want to add them in 3.0 ? 

AFAICS, the CI has been merged in 3.0 as well

> Are we planning to use Gitlab for 3.0 development as well ? Or are we 
> going to rely on the older infra with jenkins ?

I'd say we should

> 
> Is there a way to run patches through Jenkins before they are merged ?

Like 4.0, open a MR and it will run (and if it doesn't, you might still have the default location to .gitlab-ci,yml configured in your project, if you forked it before we moved it to the non-default location)

> _______________________________________________
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
> https://mailman.videolan.org/listinfo/vlc-devel

-- 
  Hugo Beauzée-Luyssen
  hugo at beauzee.fr