-
Notifications
You must be signed in to change notification settings - Fork 84
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
Update some libraries #44
Conversation
Btw, I get:
after doing |
Yes. That error is a consequence of git commit hashes not having something equivalent to SemVer. Since Servo’s glutin fork diverges from upstream, I’ve had to rename it to Until this PR is merge, you can “downgrade” your servo/glutin repo dependency to before the rename:
|
@SimonSapin Ah I see, thanks for the explanation. Much appreciated! |
Hmm, so now after this merge when I do a
However when I do:
it builds fine. So I'm not sure what's going wrong... do you get the same error? N.B. serde-deprecated/quasi#22. |
Try |
Sorry, misread your error message. Try updating your Rust nightly |
@SimonSapin That worked, thanks! But doesn't this mean that https://github.com/servo/servo/blob/master/rust-snapshot-hash should be updated? Because when I tried the above, that's the version of rustc that I had installed (i.e. 1805bba399805d8fd8e85e23c31a0580f21533cb). (Now I have updated to latest master, 69b2fce7bb2283ceb950f786c15cbbcd50787c8e, which is the one that works.) |
Also, while I can build this package in particular with 69b2fce, I can't build servo with it (rust compilation errors), whereas I could build servo with 1805bba. So is there any solution to that? Am I doing things wrong? By 'build servo', I mean:
Sorry to spam here, not sure where else to ask.. |
We use |
@jdm oh right, even for the library only? Because then how would one use |
@jdm Because see here: https://github.com/meh/miserve/blob/18bf3ca945cffa8b6f97f088f04c918e741f7dd9/Cargo.toml#L20-L22 So I figured it would work if I install the appropriate rustc version from the |
AFAIK @meh is the only one who has experimented with that, so they're in a better position to answer questions. |
Servo’s So far, I think we haven’t considered much the case of using Servo as a Rust library directly. Using many libraries that use unstable language features makes this kinda hard. I don’t know what we can do to support it better. Perhaps CEF is the answer: compile Servo as one big library with a C-compatible API, and the Rust version it uses becomes irrelevant. If the program that uses it also uses Rust, it doesn’t have to be the same version. There could be a Rust wrapper around that C-compatible API on the "client" side to make it more convenient to use. (That last part doesn’t exist yet.) |
If I recall correctly the trick I used was copying the |
@SimonSapin That makes sense, thanks for the clarification. Last time I tried, the The whole reason I've come here in the first place is because I couldn't Anyway, so currently it seems as though all such naming errors have been fixed because Yes perhaps CEF is the more reliable solution, thanks for suggesting! But I guess just using the same version of rust that servo uses also works for now. |
Yeah, these renames involved changes across repositories that work together, but didn’t all got merged at the same time. |
No description provided.