Skip to content
This repository was archived by the owner on Apr 5, 2024. It is now read-only.

Properly warn if a package lacks [lib] target #135

Merged
merged 1 commit into from
Nov 5, 2020

Conversation

Xanewok
Copy link
Member

@Xanewok Xanewok commented Nov 5, 2020

Otherwise it errors out with a "lost build artifact", which may be hard to decipher.

Discovered this when running cargo semver on a package that is only a binary - while it seems obvious (there's no public crate API in the first place), the original error message left me wondering if there is something wrong with the build artifact (e.g. internal logic error or multiple cargo instances running for the same target). Hopefully, this will make it more clear that it only works on a package with [lib] target.

cc @ibabushkin
r? @Manishearth

Otherwise it errors out with a "lost build artifact", which may be hard
to decipher.
@Manishearth Manishearth merged commit 8077576 into rust-lang:master Nov 5, 2020
@bors bors mentioned this pull request Nov 5, 2020
@Xanewok Xanewok deleted the no-lib-target branch November 5, 2020 21:05
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants