[Csnd-dev] VCPKG actions

[Csnd-dev] VCPKG actions

Date	2025-09-12 13:27
From	Victor Lazzarini <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE>
Subject	[Csnd-dev] VCPKG actions
	Many of the VCPKG actions are being very troublesome lately, failing all the time. Do we need these, beyond the Windows one that produces artefacts? These ones below at least seem to be surplus to requirements. Linux/Ubuntu build (vcpkg) MacOS build (vcpkg) MacOS build (vcpkg arm) Android build (vcpkg) The problem with this is that it's impacting on our ability to develop - the majority of failures are nothing to do with the PRs. Either someone keeps an eye on this, or I think we'll have to get rid of all the VCPKG actions except for Windows.

Date	2025-09-12 15:29
From	Steven Yi
Subject	Re: [Csnd-dev] VCPKG actions
	I think it's fine to disable them and leave the actions code in so that they can be reinstated easily if someone comes around to maintain them. On Fri, Sep 12, 2025 at 8:29 AM Victor Lazzarini <000010b17ddd988e-dmarc-request@listserv.heanet.ie> wrote: > > Many of the VCPKG actions are being very troublesome lately, failing all the time. Do we need these, beyond the Windows one that produces artefacts? These ones below at least seem to be surplus to requirements. > > Linux/Ubuntu build (vcpkg) > MacOS build (vcpkg) > MacOS build (vcpkg arm) > Android build (vcpkg) > > > The problem with this is that it's impacting on our ability to develop - the majority of failures are nothing to do with the PRs. > > Either someone keeps an eye on this, or I think we'll have to get rid of all the VCPKG actions except for Windows. > >

Date	2025-09-12 15:59
From	Werner Mendizabal
Subject	Re: [Csnd-dev] VCPKG actions
	Hello Victor, I can look into this. I am also having similar issues in my own projects that build csound using vcpkg. On Fri, Sep 12, 2025 at 7:29 AM Victor Lazzarini <000010b17ddd988e-dmarc-request@listserv.heanet.ie> wrote: Many of the VCPKG actions are being very troublesome lately, failing all the time. Do we need these, beyond the Windows one that produces artefacts? These ones below at least seem to be surplus to requirements. Linux/Ubuntu build (vcpkg) MacOS build (vcpkg) MacOS build (vcpkg arm) Android build (vcpkg) The problem with this is that it's impacting on our ability to develop - the majority of failures are nothing to do with the PRs. Either someone keeps an eye on this, or I think we'll have to get rid of all the VCPKG actions except for Windows.

Date	2025-09-12 18:34
From	Victor Lazzarini <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE>
Subject	Re: [Csnd-dev] [EXTERNAL] Re: [Csnd-dev] VCPKG actions
	Thanks. For now I have disable the two jobs that are failing all the time. Prof. Victor Lazzarini Maynooth University Ireland On 12 Sep 2025, at 15:59, Werner Mendizabal <nonameentername@gmail.com> wrote: Warning This email originated from outside of Maynooth University's Mail System. Do not reply, click links or open attachments unless you recognise the sender and know the content is safe. Hello Victor, I can look into this. I am also having similar issues in my own projects that build csound using vcpkg. On Fri, Sep 12, 2025 at 7:29 AM Victor Lazzarini <000010b17ddd988e-dmarc-request@listserv.heanet.ie> wrote: Many of the VCPKG actions are being very troublesome lately, failing all the time. Do we need these, beyond the Windows one that produces artefacts? These ones below at least seem to be surplus to requirements. Linux/Ubuntu build (vcpkg) MacOS build (vcpkg) MacOS build (vcpkg arm) Android build (vcpkg) The problem with this is that it's impacting on our ability to develop - the majority of failures are nothing to do with the PRs. Either someone keeps an eye on this, or I think we'll have to get rid of all the VCPKG actions except for Windows.