Closed xNxExOx closed 5 years ago
I encountered the same problem.
Same,. did you find a fix?
Windows support is not a priority for us, unfortunately.
It looks like the problem here is the timekeeper
dependency, which we only use for profiling. If you wanted to make a Windows build work, you could probably make including this dependency and any code related to it conditional on the platform with Rust's builtin support for conditional compilation (cfg!(windows)
etc.).
This is unfortunate. Could we put the timekeeper
dependency / profiling behind a feature
-flag? I get that windows support is not a priority, but it's almost tragic that the build breaks because of an unmaintained dependency..
I think in theory all that should be needed is for @fintelia to land https://github.com/fintelia/timekeeper/pull/3. ping?
Excellent, that just landed. Thanks @fintelia. Once a release is published I'll bump dependencies and see if CI then passes on Windows!
Just published timekeeper v0.3.1
. Sorry for the delay on this, it somehow slipped off my radar
Aww, looks like we now fail because Windows doesn't have reasonable asynchronous timers :'( https://dev.azure.com/mit-pdos/mit-pdos/_build/results?buildId=3&view=logs&s=859b8d9a-8fd6-5a5c-6f5e-f84f1990894e&j=fb8c8813-bce5-562f-fee6-ee0e905e89a4
See https://github.com/jonhoo/tokio-os-timer/issues/9
That's not going to change any time soon sadly.
Even just the server fails to build due to the jemalloc-sys dependency. BuildError.txt