Skip to content

Don't build libstd as a dylib#7353

Merged
bors merged 1 commit intorust-lang:masterfrom
alexcrichton:libstd-no-dylib
Sep 11, 2019
Merged

Don't build libstd as a dylib#7353
bors merged 1 commit intorust-lang:masterfrom
alexcrichton:libstd-no-dylib

Conversation

@alexcrichton
Copy link
Copy Markdown
Member

This commit forcibly prevents Cargo from building the std crate as a
dylib, even though libstd upstream lists a dylib crate type. We
ideally want a first-class feature for doing this one day, but for now
we can just hack around with the manifests to ensure that the dylib
crate type never shows up. Note that this is only supported for libstd,
and it's also all part of the unstable details of building std.

Closes rust-lang/wg-cargo-std-aware#35

@rust-highfive
Copy link
Copy Markdown

r? @ehuss

(rust_highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Sep 11, 2019
This commit forcibly prevents Cargo from building the `std` crate as a
`dylib`, even though libstd upstream lists a `dylib` crate type. We
ideally want a first-class feature for doing this one day, but for now
we can just hack around with the manifests to ensure that the `dylib`
crate type never shows up. Note that this is only supported for libstd,
and it's also all part of the unstable details of building std.

Closes rust-lang/wg-cargo-std-aware#35
@ehuss
Copy link
Copy Markdown
Contributor

ehuss commented Sep 11, 2019

Should be fine for now.

@bors r+

@bors
Copy link
Copy Markdown
Contributor

bors commented Sep 11, 2019

📌 Commit 70bea01 has been approved by ehuss

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 11, 2019
bors added a commit that referenced this pull request Sep 11, 2019
Don't build libstd as a `dylib`

This commit forcibly prevents Cargo from building the `std` crate as a
`dylib`, even though libstd upstream lists a `dylib` crate type. We
ideally want a first-class feature for doing this one day, but for now
we can just hack around with the manifests to ensure that the `dylib`
crate type never shows up. Note that this is only supported for libstd,
and it's also all part of the unstable details of building std.

Closes rust-lang/wg-cargo-std-aware#35
@bors
Copy link
Copy Markdown
Contributor

bors commented Sep 11, 2019

⌛ Testing commit 70bea01 with merge 4a58255...

@bors
Copy link
Copy Markdown
Contributor

bors commented Sep 11, 2019

☀️ Test successful - checks-azure
Approved by: ehuss
Pushing 4a58255 to master...

@RalfJung
Copy link
Copy Markdown
Member

Could this be used by xargo somehow? We'd also be interested in rlib-only builds.

Cc rust-lang/rust#56443

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consider not building std as a dylib.

5 participants