Open epilys opened 9 months ago
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...
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: https://github.com/rust-lang/cargo/issues/6179
Exclude from CI, at least?
Exclude from CI, at least?
I would prefer that over doing hacks that just make the daemon build a completely pointless empty binary.
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 ^
I can't build pipewire with musl, it complains
stdbool.h
is missing. I tried installingmusl-dev
and setting the library path to musl's dir in.cargo/config.toml
:but no dice. Any ideas?
Disabling default features with
--no-default-features
gives me errors fromrust-vmm
crates:Compilation errors..
```shell Compiling vhost-user-backend v0.10.1 error[E0277]: the trait bound `Originally posted by @epilys in https://github.com/rust-vmm/vhost-device/issues/493#issuecomment-1788501194