Hello! Are you someone who compiles with
crate-type = ["dylib"],
#![crate_type = "dylib"], or
--crate-type dylib? If so, I either have terrible or amazing news!
RFC 1510 has just moved into its week-long final comment period. At its core this RFC proposes changing the definition of the
dylib crate type to be more tailored towards the Rust-in-other-applications use case. This is unfortunately a breaking change, however, for anyone who uses
extern crate foo where
foo is compiled as a
dylib as that crate would now have to be compiled as an
rdylib (more details in the RFC itself).
So in general, I’m curious to get a broader survey of:
- Do you compile dynamic libraries in Rust not used for embedding Rust?
- Do you ever specify a crate type
Cargo.toml, source, or build scripts?
It’s possible to implement RFC 1510 as not a breaking change, it’d just be unfortunate to give up the name