@@ -122,6 +122,9 @@ specifies the kind of library with the following possible values:
122122- ` static ` — Indicates a static library.
123123- ` framework ` — Indicates a macOS framework. This is only valid for macOS
124124 targets.
125+ - ` raw-dylib ` - Indicates a dynamic library where the compiler will generate
126+ an import library to link against (see [ ` dylib ` versus ` raw-dylib ` ] below
127+ for details). This is only valid for Windows targets.
125128
126129The ` name ` key must be included if ` kind ` is specified.
127130
@@ -198,9 +201,25 @@ The default for this modifier is `-whole-archive`.
198201More implementation details about this modifier can be found in
199202[ ` whole-archive ` documentation for rustc] .
200203
204+ #### ` dylib ` versus ` raw-dylib `
205+
206+ On Windows, linking against a dynamic library requires that an import library
207+ is provided to the linker: this is a special static library that declares all
208+ of the symbols exported by the dynamic library in such a way that the linker
209+ knows that they have to be dynamically loaded at runtime.
210+
211+ Specifying ` kind = "dylib" ` instructs the Rust compiler to link an import
212+ library based on the ` name ` key, the linker will then use its normal library
213+ resolution logic to find that import library. Alternatively, specifying
214+ ` kind = "raw-dylib" ` instructs the compiler to generate an import library
215+ during compilation and provide that to the linker instead.
216+
217+ ` raw-dylib ` is only supported on Windows. Using it when targeting other
218+ platforms will result in a compiler error.
219+
201220### The ` link_name ` attribute
202221
203- The ` link_name ` attribute may be specified on declarations inside an ` extern `
222+ The * ` link_name ` attribute* may be specified on declarations inside an ` extern `
204223block to indicate the symbol to import for the given function or static. It
205224uses the [ _ MetaNameValueStr_ ] syntax to specify the name of the symbol.
206225
@@ -211,6 +230,41 @@ extern {
211230}
212231```
213232
233+ Using this attribute with the ` link_ordinal ` attribute will result in a
234+ compiler error.
235+
236+ ### The ` link_ordinal ` attribute
237+
238+ The * ` link_ordinal ` attribute* can be applied on declarations inside an ` extern `
239+ block to indicate the numeric ordinal to use when generating the import library
240+ to link against. An ordinal is a unique number per symbol exported by a dynamic
241+ library on Windows and can be used when the library is being loaded to find
242+ that symbol rather than having to look it up by name.
243+
244+ <div class =" warning " >
245+
246+ Warning: ` link_ordinal ` should only be used in cases where the ordinal of the
247+ symbol is known to be stable: if the ordinal of a symbol is not explicitly set
248+ when its containing binary is built then one will be automatically assigned to
249+ it, and that assigned ordinal may change between builds of the binary.
250+
251+ </div >
252+
253+ <!-- ignore: Only works on x86 Windows -->
254+ ``` rust,ignore
255+ #[link(name = "exporter", kind = "raw-dylib")]
256+ extern "stdcall" {
257+ #[link_ordinal(15)]
258+ fn imported_function_stdcall(i: i32);
259+ }
260+ ```
261+
262+ This attribute is only used with the ` raw-dylib ` linking kind.
263+ It is ignored if used with any other kind.
264+
265+ Using this attribute with the ` link_name ` attribute will result in a
266+ compiler error.
267+
214268### Attributes on function parameters
215269
216270Attributes on extern function parameters follow the same rules and
@@ -233,3 +287,4 @@ restrictions as [regular function parameters].
233287[ regular function parameters ] : functions.md#attributes-on-function-parameters
234288[ `bundle` documentation for rustc ] : ../../rustc/command-line-arguments.html#linking-modifiers-bundle
235289[ `whole-archive` documentation for rustc ] : ../../rustc/command-line-arguments.html#linking-modifiers-whole-archive
290+ [ `dylib` versus `raw-dylib` ] : #dylib-versus-raw-dylib
0 commit comments