-
Notifications
You must be signed in to change notification settings - Fork 743
publish rust-bindgen to crates.io #252
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
Comments
Maybe #21 needs to be solved first. |
Probably we can publish as |
Actually, probably it's a better idea to wait for #204 to land. |
Would it be possible to publish this now, since #204 has landed? |
Yes, I'm still fixing some fallout from recent changes, but when it's
stable enough I'll publish it.
…On Tue, Nov 22, 2016 at 03:37:02AM -0800, Elliott Linder wrote:
Would it be possible to publish this now, since #204 has landed?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#252 (comment)
|
After #327 I thought we would be good to publish
I think |
Libbindgen is published now at https://crates.io/crates/libbindgen :) Stylo is going to need to use it from there. @darfink let me know if you also want the binary published. |
Cleanup some warnings from Clippy
Firefox has a mechanism for importing crates into its source tree, which depends on
cargo vendor
.cargo vendor
, in turn, expects everything to be published oncrates.io
. (Yes, yes, we could point it at a different crate registry, but that has its own set of problems.)rust-bindgen
will eventually need to be imported into mozilla-central so thatrust-bindgen
can be run on every build.Ergo, it would be splendid if
rust-bindgen
were published tocrates.io
so the import could be accomplished with minimal hassle.The text was updated successfully, but these errors were encountered: