diff options
| author | Steve Klabnik <steve@steveklabnik.com> | 2015-06-09 15:17:25 -0400 |
|---|---|---|
| committer | Steve Klabnik <steve@steveklabnik.com> | 2015-06-09 15:17:30 -0400 |
| commit | a9899a73533c542efcc797405e3c09882da9d7fa (patch) | |
| tree | 7ceff1c410f46e44660602dceb405e7dcc2e54de | |
| parent | 7b0f2af27f18b6c81fe6a2faab0ba96e0da3bba5 (diff) | |
Clarify confusing sentence in TRPL: FFI
After talking with @graydon on #rust-internals, this is hopefully clarifying. Fixes #25586
| -rw-r--r-- | src/doc/trpl/ffi.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/src/doc/trpl/ffi.md b/src/doc/trpl/ffi.md index 9ede835e521..8077f04ed60 100644 --- a/src/doc/trpl/ffi.md +++ b/src/doc/trpl/ffi.md @@ -342,8 +342,10 @@ Note that frameworks are only available on OSX targets. The different `kind` values are meant to differentiate how the native library participates in linkage. From a linkage perspective, the rust compiler creates two flavors of artifacts: partial (rlib/staticlib) and final (dylib/binary). -Native dynamic libraries and frameworks are propagated to the final artifact -boundary, while static libraries are not propagated at all. +Native dynamic library and framework dependencies are propagated to the final +artifact boundary, while static library dependencies are not propagated at +all, because the static libraries are integrated directly into the subsequent +artifact. A few examples of how this model can be used are: |