@@ -122,6 +122,9 @@ specifies the kind of library with the following possible values:
122
122
- ` static ` — Indicates a static library.
123
123
- ` framework ` — Indicates a macOS framework. This is only valid for macOS
124
124
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.
125
128
126
129
The ` name ` key must be included if ` kind ` is specified.
127
130
@@ -198,6 +201,19 @@ The default for this modifier is `-whole-archive`.
198
201
More implementation details about this modifier can be found in
199
202
[ ` whole-archive ` documentation for rustc] .
200
203
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
+
201
217
### The ` link_name ` attribute
202
218
203
219
The ` link_name ` attribute may be specified on declarations inside an ` extern `
@@ -211,6 +227,40 @@ extern {
211
227
}
212
228
```
213
229
230
+ Using this attribute with the ` link_ordinal ` attribute will result in a
231
+ compiler error.
232
+
233
+ ### The ` link_ordinal ` attribute
234
+
235
+ This attribute is only used with the ` raw-dylib ` linking kind.
236
+ It is ignored if used with any other kind.
237
+
238
+ On Windows, symbols exported from a dynamic library can either be found using
239
+ their name or by a unique number call an "ordinal". The ` link_ordinal `
240
+ attribute can be applied on declarations inside an ` extern ` block to indicate
241
+ the ordinal to use when generating the import library to link against.
242
+
243
+ <div class =" warning " >
244
+
245
+ Warning: ` link_ordinal ` should only be used in cases where the ordinal of the
246
+ symbol is known to be stable: if the ordinal of a symbol is not explicitly set
247
+ when its containing binary is built then one will be automatically assigned to
248
+ it, and that assigned ordinal may change between builds of the binary.
249
+
250
+ </div >
251
+
252
+ <!-- ignore: Only works on x86 Windows -->
253
+ ``` rust,ignore
254
+ #[link(name = "exporter", kind = "raw-dylib")]
255
+ extern "stdcall" {
256
+ #[link_ordinal(15)]
257
+ fn imported_function_stdcall(i: i32);
258
+ }
259
+ ```
260
+
261
+ Using this attribute with the ` link_name ` attribute will result in a
262
+ compiler error.
263
+
214
264
### Attributes on function parameters
215
265
216
266
Attributes on extern function parameters follow the same rules and
@@ -233,3 +283,4 @@ restrictions as [regular function parameters].
233
283
[ regular function parameters ] : functions.md#attributes-on-function-parameters
234
284
[ `bundle` documentation for rustc ] : ../../rustc/command-line-arguments.html#linking-modifiers-bundle
235
285
[ `whole-archive` documentation for rustc ] : ../../rustc/command-line-arguments.html#linking-modifiers-whole-archive
286
+ [ `dylib` versus `raw-dylib` ] : #dylib-versus-raw-dylib
0 commit comments