No output library created when using workspaces

[phil-opp]

Example Project (git repo):

Cargo.toml:

[package]
authors = ["Philipp Oppermann <dev@phil-opp.com>"]
name = "issue"
version = "0.1.0"

[dependencies.foo]
path = "libs/foo"

[workspace]

libs/foo/Cargo.toml:

[package]
authors = ["Philipp Oppermann <dev@phil-opp.com>"]
name = "foo"
version = "0.1.0"

src/lib.rs and libs/foo/src/lib.rs are both empty.

When I run cargo build, there is no output rlib in target/debug. It works if I remove the workspace from the Cargo.toml.

cargo 0.16.0-nightly (ddb5c32 2016-12-16)
rustc 1.15.0-nightly (8f02c429a 2016-12-15)

[alexcrichton]

Interesting! There was a change that tweaked how we managed the output directory structure, but I thought it didn't bring rlibs into place at all. Apparently it happens at least for non-workspace projects!

I suspect there's an extraneous check somewhere that just needs to be updated now that workspaces are in play.

[steveatinfincia]

I think I've hit this as well, but with a static lib output. It's clearly being built in deps (though with a bunch of numbers after the name of the library), it just never makes it to target/release or target/debug. Is b2ed772 expected to apply there?

[alexcrichton]

@steveatinfincia I believe so, indeed!