-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows build regularly gets broken #102
Comments
@SimonSapin, I think that build actually broke with #99, when |
@jaxx yes, probably. But the deeper problem is that we have code that I never build or test, so it inevitably breaks. |
SimonSapin
added a commit
that referenced
this issue
May 4, 2015
93bc3d1 should avoid most of these issues. |
http://www.appveyor.com/ could help as well. Anyone want to try it? CC @jaxx @fuchsnj @alexcrichton |
We’re now testing on Windows with Appveyor: #105 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since the
std::path
reform, that module switched to having a singlePath
type with conditionally-compiled platform-specific behavior instead of separatestd::path::unix::Path
andstd::path::windows::Path
types and only a platform-specific re-export asstd::path::Path
.rust-url also has some platform specific behavior for converting between
Path
andfile://
URLs. Previously, we could implement traits for bothPath
types and have that code exist and all platforms. Now that it’s a single type, we have to use#[cfg(…)]
to do conditional compilation too.This is a long way to say that we now have Windows-specific code that is not compiled on Unix. Since I don’t use Windows and Windows is not available on Travis-CI, this code often gets broken without me noticing: #89, #96, #101.
The text was updated successfully, but these errors were encountered: