starred/spotify-player

Fork 0

mirror of https://github.com/aome510/spotify-player.git synced 2026-04-26 09:25:49 +03:00

[GH-ISSUE #628] Cannot install with sixel lib #1300

New issue

Open

opened 2026-03-14 14:19:35 +03:00 by kerem · 4 comments

kerem commented

2026-03-14 14:19:35 +03:00

Owner

Originally created by @minhquan186 on GitHub (Dec 7, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/628

Describe the bug
Cannot Install spotify_player with sixel support on Windows 10 using cargo

To Reproduce
Run cargo install spotify_player --features lyric-finder,sixel

Expected behaviour
Install spotify_player with sixel support successfully.

Log and backtrace
Installation problem, no log needed

Screenshots

Environment

OS: Windows
Application version: v0.20.3
Application features: lyric-finder, sixel

Additional context
I'm using Windows Terminal Preview 1.22.2912.0 which has libsixel supported (see this blog)
If I use cargo install spotify_player --features lyric-finder,image I can install and use it normally

Originally created by @minhquan186 on GitHub (Dec 7, 2024). Original GitHub issue: https://github.com/aome510/spotify-player/issues/628 **Describe the bug** Cannot Install `spotify_player` with `sixel` support on Windows 10 using `cargo` **To Reproduce** Run `cargo install spotify_player --features lyric-finder,sixel` **Expected behaviour** Install `spotify_player` with `sixel` support successfully. **Log and backtrace** Installation problem, no log needed **Screenshots** ![image](https://github.com/user-attachments/assets/25d0e510-2da6-4b8c-997d-902bc79f94a8) **Environment** - OS: Windows - Application version: v0.20.3 - Application features: lyric-finder, sixel **Additional context** I'm using Windows Terminal Preview 1.22.2912.0 which has libsixel supported (see [this blog](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-22-release/#sixel-image-support)) If I use `cargo install spotify_player --features lyric-finder,image` I can install and use it normally

kerem added the

bug

label

2026-03-14 14:19:35 +03:00

kerem commented

2026-03-14 14:19:46 +03:00

Author

Owner

@aome510 commented on GitHub (Dec 8, 2024):

I don't really know much about sixel support for windows. Maybe the library sixel-sys doesn't support windows

@aome510 commented on GitHub (Dec 8, 2024): I don't really know much about sixel support for windows. Maybe the library `sixel-sys` doesn't support windows

kerem commented

2026-03-14 14:19:51 +03:00

Author

Owner

@minhquan186 commented on GitHub (Dec 16, 2024):

I think sixel-sys could be an issue here.
I use another program (chafa) with sixel supported and it works fine

Could you also double check the version of sixel-sys that used in spotify_player?
Thanks in advance

@minhquan186 commented on GitHub (Dec 16, 2024): I think `sixel-sys` could be an issue here. I use another program ([chafa](https://hpjansson.org/chafa/)) with sixel supported and it works fine ![image](https://github.com/user-attachments/assets/dfadaf6f-8fab-4b1b-a2be-49b4827a965f) Could you also double check the version of `sixel-sys` that used in `spotify_player`? Thanks in advance

kerem commented

2026-03-14 14:19:56 +03:00

Author

Owner

@csoto-3 commented on GitHub (Dec 10, 2025):

Tried to install from cargo with sixel feature and still having issues with sixel-sys on Win11.

Command: cargo install spotify_player --features sixel

Error Message:

error: failed to run custom build command for `sixel-sys v0.3.1`

Caused by:
  process didn't exit successfully: `C:\Users\<username>\AppData\Local\Temp\cargo-installaMTwyK\release\build\sixel-sys-3661e2ae4dca7018\build-script-build` (exit code: 101)
  --- stdout
  cargo:rustc-link-lib=dylib=sixel
  cargo:rustc-link-search=native=C:\Users\<username>\AppData\Local\Temp\cargo-installaMTwyK\release\build\sixel-sys-36e8ad30817be80f\out\lib

  --- stderr

  thread 'main' (22080) panicked at C:\Users\<username>\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\sixel-sys-0.3.1\build.rs:71:22:
  Failed to execute ./configure: Os { code: 2, kind: NotFound, message: "The system cannot find the file specified." }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile `spotify_player v0.21.2`, intermediate artifacts can be found at `C:\Users\<username>\AppData\Local\Temp\cargo-installaMTwyK`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

@csoto-3 commented on GitHub (Dec 10, 2025): Tried to install from `cargo` with `sixel` feature and still having issues with `sixel-sys` on Win11. Command: `cargo install spotify_player --features sixel` Error Message: ``` error: failed to run custom build command for `sixel-sys v0.3.1` Caused by: process didn't exit successfully: `C:\Users\<username>\AppData\Local\Temp\cargo-installaMTwyK\release\build\sixel-sys-3661e2ae4dca7018\build-script-build` (exit code: 101) --- stdout cargo:rustc-link-lib=dylib=sixel cargo:rustc-link-search=native=C:\Users\<username>\AppData\Local\Temp\cargo-installaMTwyK\release\build\sixel-sys-36e8ad30817be80f\out\lib --- stderr thread 'main' (22080) panicked at C:\Users\<username>\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\sixel-sys-0.3.1\build.rs:71:22: Failed to execute ./configure: Os { code: 2, kind: NotFound, message: "The system cannot find the file specified." } note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace warning: build failed, waiting for other jobs to finish... error: failed to compile `spotify_player v0.21.2`, intermediate artifacts can be found at `C:\Users\<username>\AppData\Local\Temp\cargo-installaMTwyK`. To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path. ```

kerem commented

2026-03-14 14:20:01 +03:00

Author

Owner

@rashil2000 commented on GitHub (Dec 23, 2025):

See https://github.com/atanunq/viuer/pull/84#issuecomment-3483860255

@rashil2000 commented on GitHub (Dec 23, 2025): See https://github.com/atanunq/viuer/pull/84#issuecomment-3483860255