about summary refs log tree commit diff
path: root/src/rustllvm/RustWrapper.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2013-11-30 14:41:40 -0800
committerbors <bors@rust-lang.org>2013-11-30 14:41:40 -0800
commit4252a24ae1236207a99c1d313d4b1b1eda3ebb58 (patch)
treec0b36a1a14bf504be40acb188934e65497745848 /src/rustllvm/RustWrapper.cpp
parentdfe46f788bd080fed67c63e7a04dad10468502b3 (diff)
parent56e4c82a38cfb2bcf7de2d6323dab0073a70726d (diff)
downloadrust-4252a24ae1236207a99c1d313d4b1b1eda3ebb58.tar.gz
rust-4252a24ae1236207a99c1d313d4b1b1eda3ebb58.zip
auto merge of #10528 : alexcrichton/rust/static-linking-v2, r=pcwalton
In this series of commits, I've implemented static linking for rust. The scheme I implemented was the same as my [mailing list post](https://mail.mozilla.org/pipermail/rust-dev/2013-November/006686.html).

The commits have more details to the nitty gritty of what went on. I've rebased this on top of my native mutex pull request (#10479), but I imagine that it will land before this lands, I just wanted to pre-emptively get all the rebase conflicts out of the way (becuase this is reorganizing building librustrt as well).

Some contentious points I want to make sure are all good:

* I've added more "compiler chooses a default" behavior than I would like, I want to make sure that this is all very clearly outlined in the code, and if not I would like to remove behavior or make it clearer.
* I want to make sure that the new "fancy suite" tests are ok (using make/python instead of another rust crate)

If we do indeed pursue this, I would be more than willing to write up a document describing how linking in rust works. I believe that this behavior should be very understandable, and the compiler should never hinder someone just because linking is a little fuzzy.
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions