3 The tracking issue for this feature is: [#29596]
5 [#29596]: https://github.com/rust-lang/rust/issues/29596
7 ------------------------
9 You can tell `rustc` how to customize linking, and that is via the `link_args`
10 attribute. This attribute is applied to `extern` blocks and specifies raw flags
11 which need to get passed to the linker when producing an artifact. An example
15 #![feature(link_args)]
17 #[link_args = "-foo -bar -baz"]
22 Note that this feature is currently hidden behind the `feature(link_args)` gate
23 because this is not a sanctioned way of performing linking. Right now `rustc`
24 shells out to the system linker (`gcc` on most systems, `link.exe` on MSVC), so
25 it makes sense to provide extra command line arguments, but this will not
26 always be the case. In the future `rustc` may use LLVM directly to link native
27 libraries, in which case `link_args` will have no meaning. You can achieve the
28 same effect as the `link_args` attribute with the `-C link-args` argument to
31 It is highly recommended to *not* use this attribute, and rather use the more
32 formal `#[link(...)]` attribute on `extern` blocks instead.