Problems with building `vhost-device-sound` in musl about rust-vmm-ci

[epilys]

Exclude from CI, at least?

[stefano-garzarella]

Is there a way to exclude some projects from a workspace depending on the target architecture? That would seem like the simplest way out to me...

@Ablu It looks like they are still discussing that: rust-lang/cargo#6179

[Ablu]

While I am not sure what the musl support situation is for pipewire, we have other crates - like vhost-device-gpio, that just do not have musl support. So I would be all for allowing crates to opt out of musl building. In vhost-device-gpio we just #[cfg(...)] the entire main away, but building an empty daemon for musl targets makes little sense to me.

Is there a way to exclude some projects from a workspace depending on the target architecture? That would seem like the simplest way out to me...

[Ablu]

Exclude from CI, at least?

I would prefer that over doing hacks that just make the daemon build a completely pointless empty binary.

[stefano-garzarella]

Exclude from CI, at least?

I would prefer that over doing hacks that just make the daemon build a completely pointless empty binary.

Yeah, me too. But I'm not sure if we have a way other than writing our own custom pipeline.
@andreeaflorescu ^