You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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 forrustc-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 invokingcargo
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.The text was updated successfully, but these errors were encountered: