Hi all — I’m trying to build a Rust project that depends on `mediasoup-sys = “0.10.0”` (mediasoup `“0.20.0”`) on Windows 11, and the build repeatedly fails in the Meson/Ninja step.
- Operating system: Windows 11 (build 26200)
- Shell: Developer PowerShell for Visual Studio
- MSVC: cl 19.44.35217 (VS 17.14.17), link 14.44.35217.0
- Meson: 1.5.0
- Ninja: 1.10.2.git.kitware.jobserver-1
- Python: 3.11.9 (pyenv)
- Long paths: enabled
- Not under OneDrive/Dropbox; no indexers; no custom `MESON_ARGS`/`NINJAFLAGS`/`CL`/`LINK`
Command:
- `cargo build` inside the project directory
Error (repeats):
```text
ninja: error: manifest ‘build.ninja’ still dirty after 100 tries
thread ‘main’ panicked at …\mediasoup-sys-0.10.0\build.rs:154:9:
Failed to build libmediasoup-worker
```
Tried:
- `cargo clean` and deleting `target/debug/build/mediasoup-sys-*/out` → same error
- Running the wrapper: `meson compile -C C:\Users\Path\to\file\Desktop\…\out\build` → same error
- Confirmed long paths and MSVC environment are active
I would really appreciate someone’s help, as I’m not really sure what’s causing this issue.
This forum is for usage questions. GitHub is for reporting bugs/issues in the software. Yours seems to be 100% reproducible so let’s handle it as a bug (although nobody here is using Windows so it’s hard to solve).
Okay then, (after you reply) I’ll remove the post from here.
Since we can handle this as a bug, please let me know if there’re any tools/steps I can take to help debug the issue (especially since, like you mentioned, no one uses Windows).
Taking a peak right now, I may have a patch so it will build on any OS; just need to test things on Windows 10 and 11. Should have some results in 30-60 minutes.
So far got it compiling on Windows 10 few issues though, need to trick meson/ninja a bit. I’ll see how far I get with this tonight if it takes longer.
This topic is not about mediasoup building errors due to C++ code. I mean, Windows CI passes. The topic here is about mediasoup crate failing to install in a Rust project in Windows.
Did you manage to reproduce the problem by following the STR given by the user?
If so, will you write a PR fixing it?
Note: please, don’t answer here. There is an open issue in GitHub (see comments above).