about summary refs log tree commit diff
path: root/src/test/rustdoc-ui/coverage/json.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2020-01-25 07:49:40 +0000
committerbors <bors@rust-lang.org>2020-01-25 07:49:40 +0000
commit80a65bcaf2f2b8a5c659b21b32b42bc300338a0e (patch)
tree52525b3dfbde41746b2b9b3c9122393574fd3b56 /src/test/rustdoc-ui/coverage/json.rs
parent8bf17584e01d85c631bcb19b7cd0f95e84c9a9b1 (diff)
parent72aaa3a414d17aa0c4f19feafa5bab5f84b60e63 (diff)
downloadrust-80a65bcaf2f2b8a5c659b21b32b42bc300338a0e.tar.gz
rust-80a65bcaf2f2b8a5c659b21b32b42bc300338a0e.zip
Auto merge of #68448 - maurer:dyn-cdylib, r=alexcrichton
rustc: Allow cdylibs to link against dylibs

Previously, rustc mandated that cdylibs could only link against rlibs as dependencies (not dylibs).
This commit disables that restriction and tests that it works in a simple case.

I don't have a windows rustc dev environment, so I guessed at the MSVC test code, I'm hoping the CI can run that for me.

Additionally, we might want to consider emitting (through cargo or rustc) some metadata to help C users of a cdylib figure out where all the dylibs they need are. I don't think that should be needed to land this change, as it will still be usable by homogeneous build systems without it.

My new test was templated off the `tests/run-make-fulldeps/cdylib` test. It seemed more appropriate to have it as a separate test, since both foo.rs and bar.rs would need to be replicated to make that test cover both cases, but I can do that if it would be preferred.

If I'm doing anything out of order/process, please let me know; this is only my second change to rustc and the prior one was trivial.

r? alexcrichton
Diffstat (limited to 'src/test/rustdoc-ui/coverage/json.rs')
0 files changed, 0 insertions, 0 deletions