about summary refs log tree commit diff
path: root/src/libstd/str.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2014-05-06 19:46:44 -0700
committerbors <bors@rust-lang.org>2014-05-06 19:46:44 -0700
commit24f6f26e633e50b5b59f9d0f6cca0b1e49e215d9 (patch)
tree79a5920acbd90f0d55fed42edc81abe118235056 /src/libstd/str.rs
parentb299231d1252d8ac74bc0b1650731ec5c2c0fdb7 (diff)
parenta82f92177595324f50f28b257ec1a079e04f631b (diff)
downloadrust-24f6f26e633e50b5b59f9d0f6cca0b1e49e215d9.tar.gz
rust-24f6f26e633e50b5b59f9d0f6cca0b1e49e215d9.zip
auto merge of #13892 : alexcrichton/rust/mixing-rlib-dylib-deps, r=brson
Currently, rustc requires that a linkage be a product of 100% rlibs or 100%
dylibs. This is to satisfy the requirement that each object appear at most once
in the final output products. This is a bit limiting, and the upcoming libcore
library cannot exist as a dylib, so these rules must change.

The goal of this commit is to enable *some* use cases for mixing rlibs and
dylibs, primarily libcore's use case. It is not targeted at allowing an
exhaustive number of linkage flavors.

There is a new dependency_format module in rustc which calculates what format
each upstream library should be linked as in each output type of the current
unit of compilation. The module itself contains many gory details about what's
going on here.

cc #10729
Diffstat (limited to 'src/libstd/str.rs')
0 files changed, 0 insertions, 0 deletions