Add --extern foo=path command line flag
#14469
Comments
Merged
bors
added a commit
that referenced
this issue
Jul 5, 2014
This is an implementation of [RFC 35](https://github.com/rust-lang/rfcs/blob/master/active/0035-remove-crate-id.md). The summary for this PR is the same as that of the RFC, with one addendum: * Removes the `#[crate_id]` attribute and knowledge of versions from rustc. * Added a `#[crate_name]` attribute similar to the old `#[crate_id]` attribute * Output filenames no longer have versions or hashes * Symbols no longer have versions (they still have hashes) * A new flag, `--extern`, is used to override searching for external crates * A new flag, `-C metadata=foo`, used when hashing symbols * [added] An old flag, `--crate-name`, was re purposed to specify the crate name from the command line. I tried to maintain backwards compatibility wherever possible (with warnings being printed). If I missed anywhere, however, please let me know! [breaking-change] Closes #14468 Closes #14469 Closes #14470 Closes #14471
|
Does it make sense for the |
|
Yes, in general |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
cc #14468
Add a command line flag to let tools like cargo specify exactly which library to use for an
extern cratestatement.It looks like
--extern foo=path, where "foo" is the name of a crate, and path is the path of a rust library, without the extension (so it will look for both.rliband.dylib).The text was updated successfully, but these errors were encountered: