mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Clarify confusing sentence in TRPL: FFI

Browse Source 
After talking with @graydon on #rust-internals, this is hopefully clarifying.

Fixes #25586
This commit is contained in:
Steve Klabnik 2015-06-09 15:17:25 -04:00
parent 7b0f2af27f
commit a9899a7353
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/doc/trpl/ffi.md
View File

@ -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: