-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Re-add a hash to the filename at the top level to avoid conflicts with external libs? #1601
Comments
Thanks for opening an issue! My concrete idea here was something like: [lib]
name = "..."
extra-filename = "-rust" Where |
As there hasn't been any activity here in a while would someone (the author, a team member, or any interested party) be able to summarise the current state, perhaps making explicit:
Thank you! (The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.) If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable! |
This is still a relevant issue. Here is my attempt to compile the default hello-world template using the musl target:
|
This is a follow up to this issue from the rust repo after amazing detective work by @alexcrichton :)
It seems that although 27efa7b correctly points out that it is impossible for conflicts to arise between rust crates, it is still possible for conflicts to arise between external libraries and cargo produced libraries.
This may prove to be a confusing/surprising issue for authors of rust libraries that bind to external / non-cargo produced libraries. It is likely not uncommon for an author to name their crate the same as the external library which they wrap for ease of search-ability. As an example, this is the exact issue we've just run into in the rust-portaudio crate.
Possible solutions:
Personally I'm in favour of 1, though I'm not familiar enough with cargo to understand entirely what is involved :)
Thanks again Alex for the great job on debugging this one!
The text was updated successfully, but these errors were encountered: