LiveKit Community

the errors started showing up on a fork i hadn't changed in a couple of months, i suspect due to the github win image being updated

seems like this issue occurs building against the main repo (<https://github.com/livekit/rust-sdks/commit/c7a431b8c3e2abc45072daf32b13a5faaf14c854|c7a431b>) as well

and also against <http://crates.io|crates.io> 0.2

pls let me know if a minimal repro would help at all

Seems related to <https://github.com/livekit/rust-sdks/issues/249>

could well be related... i don't have the `FILE_INFO_BY_HANDLE_CLASS` errors (example action results at <<https://github.com/decentraland/bevy-explorer/actions/runs/6986152904/job/19011288602>>, built against <http://crates.io|crates.io> - far from minimal though)

Do you have the same error if you build webrtc yourself using <https://github.com/livekit/rust-sdks/blob/main/webrtc-sys/libwebrtc/build_windows.cmd|build_windows.cmd> ?

locally i can't build from crates due to long-paths, but if i modify it i can still build locally

locally i have msvc 14.36.32532, vs github 14.38.33130

(i tried the github windows-2019 image as well, but it fails with other errors like `unresolved external symbol __std_find_trivial_8` )

Having the same issue here
<https://github.com/livekit/rust-sdks/actions/runs/7034281499/job/19141959220>

We’ve worked around it using a self-hosted runner for now