docs: recommend at least one audio and discovery backend (#1390)

This commit is contained in:
Roderick van Domburg 2024-11-03 20:15:48 +01:00
parent e2eca65d11
commit 82076e882f
No known key found for this signature in database
GPG key ID: FE2585E713F9F30A

View file

@ -97,15 +97,17 @@ You will most likely want to build debug builds when developing, as they compile
There are also a number of compiler feature flags that you can add, in the event that you want to have certain additional features also compiled. The list of these is available on the [wiki](https://github.com/librespot-org/librespot/wiki/Compiling#addition-features). There are also a number of compiler feature flags that you can add, in the event that you want to have certain additional features also compiled. The list of these is available on the [wiki](https://github.com/librespot-org/librespot/wiki/Compiling#addition-features).
By default, librespot compiles with the ```rodio-backend``` feature. To compile without default features, you can run with: By default, librespot compiles with the ```rodio-backend``` and ```with-libmdns``` features. To compile without default features, you can run with:
```bash ```bash
cargo build --no-default-features cargo build --no-default-features
``` ```
Similarly, to build with the ALSA backend: Note that this will also disable zeroconf discovery backends for Spotify Connect. For normal use cases, select at least one audio and discovery backend.
For example, to build with the ALSA audio and libmdns discovery backend:
```bash ```bash
cargo build --no-default-features --features "alsa-backend" cargo build --no-default-features --features "alsa-backend with-libmdns"
``` ```
### Running ### Running