No Windows binary is being generated

[rafaellehmkuhl]

This is due to the moving to Bun.

Patrick suggested using Yarn to build the Windows version.

[rafaellehmkuhl]

@patrickelectric can you take a look at that when possible?
Brian was asking for a Windows binary, but we don't have an updated one anymore.

[rafaellehmkuhl]

@patrickelectric since you were already working with the CI for the flatpak deployment, could you also take a look at this one?

[patrickelectric]

We have both extension and the website: https://blueos.cloud/cockpit
Is there a need right now for windows artifacts ?

[rafaellehmkuhl]

We have both extension and the website: https://blueos.cloud/cockpit Is there a need right now for windows artifacts ?

Someone not directly using BlueOS or without an internet connection.

But more important than that is so we do not start with the wrong foot deprecating one system over another in a project that sells itself as natively cross-platform.

[Williangalvani]

I also suspect that https cockpit won't be able to task to unsecure mavlink over ws, will it?

[rafaellehmkuhl]

I also suspect that https cockpit won't be able to task to unsecure mavlink over ws, will it?

I think it is possible if the unsecure mavlink is served locally. Browsers do ignore security check on localhost paths for most things.

But independent of that, I think it is a big mistake for us to treat any of the three main desktop OSs in a different way, as we are doing with Windows right now.

We should either have binaries for all of them, or for none.