Skip to content
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

Publish rustc-demangle-capi on crates.io #44

Closed
maurer opened this issue Feb 2, 2021 · 4 comments
Closed

Publish rustc-demangle-capi on crates.io #44

maurer opened this issue Feb 2, 2021 · 4 comments

Comments

@maurer
Copy link

maurer commented Feb 2, 2021

Right now, rustc-demangle-capi only exists as a subdirectory of this repository. In Android, we've been using crates.io as our primary source of third party packages, and it would be nice for rustc-demangle to not be an exception.

I could upload it myself, but I figured that Crichton should probably own the package.

For other users, making this crate available would also make it easier to pull into their builds, whether through a rules_rust style build in Bazel or by invoking cargo to build the .a or .so they need from crates.io or a cargo vendor directory. It also makes sense given rust-lang/rfcs#3028 which makes these possibly useful artifacts to a Cargo build.

@alexcrichton
Copy link
Member

Sure thing! Published now

@krtab
Copy link

krtab commented Feb 4, 2021

Hi!

I am a bit confused with regards to two points:

  1. What does this change add/provides?
  2. What is now the preferred way to package the C API of rustc-demangle? I'm packaging it for the AUR and I'm not sure whether or not I should switch to this new crate.

Thanks

@alexcrichton
Copy link
Member

This published the crate on crates.io. You can use it if you'd like, you also don't have to use it. I don't know enough about packaging to advise how to package this.

@krtab
Copy link

krtab commented Feb 4, 2021

Thanks for the answer. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants