Skip to content

Commit

Permalink
Rollup merge of #104549 - folkertdev:unstable-book-export-executable-…
Browse files Browse the repository at this point in the history
…symbols, r=WaffleLapkin

add -Zexport-executable-symbols to unstable book

This flag has been extremely useful to me, but it's hard to discover. The text contains a bunch of terms that hopefully a search engine will pick up on when someone searches for this functionality.
  • Loading branch information
matthiaskrgr authored Mar 3, 2023
2 parents 7a809ce + f53b364 commit a8b9f47
Showing 1 changed file with 43 additions and 0 deletions.
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
# `export-executable-symbols`

The tracking issue for this feature is: [#84161](https://github.com/rust-lang/rust/issues/84161).

------------------------

The `-Zexport-executable-symbols` compiler flag makes `rustc` export symbols from executables. The resulting binary is runnable, but can also be used as a dynamic library. This is useful for interoperating with programs written in other languages, in particular languages with a runtime like Java or Lua.

For example on windows:
```rust
#[no_mangle]
fn my_function() -> usize {
return 42;
}

fn main() {
println!("Hello, world!");
}
```

A standard `cargo build` will produce a `.exe` without an export directory. When the `export-executable-symbols` flag is added

```Bash
export RUSTFLAGS="-Zexport-executable-symbols"
cargo build
```

the binary has an export directory with the functions:

```plain
The Export Tables (interpreted .edata section contents)
...
[Ordinal/Name Pointer] Table
[ 0] my_function
[ 1] main
```
(the output of `objdump -x` on the binary)

Please note that the `#[no_mangle]` attribute is required. Without it, the symbol is not exported.

The equivalent of this flag in C and C++ compilers is the `__declspec(dllexport)` annotation or the `-rdynamic` linker flag.

0 comments on commit a8b9f47

Please sign in to comment.