Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to access binary-only crate refinery-cli #391

Closed
rahulmutt opened this issue Mar 4, 2021 · 1 comment
Closed

Unable to access binary-only crate refinery-cli #391

rahulmutt opened this issue Mar 4, 2021 · 1 comment

Comments

@rahulmutt
Copy link

rahulmutt commented Mar 4, 2021

I'm trying to get access to the binary only crate refinery-cli:

# Cargo.toml

[dependencies]
refinery_cli = "0.5.0"

[package.metadata.raze.crates.refinery_cli.'0.5.0']
extra_aliased_targets = [
    "cargon_bin_refinery"
]

And cargo raze gives me:

Found unused raze crate settings for `refinery_cli`

I also observed that there is no generated build file for refinery-cli anywhere in the cargo/remote folder. There was another create that contained both library & binaries (aeron-rs) and I was able to successfully access the binary from that one, so I wonder if fact that it is a binary-only crate is messing up raze's resolution somehow.

@rahulmutt rahulmutt changed the title Unable to access binary-only create refinery-cli Unable to access binary-only crate refinery-cli May 24, 2021
@rahulmutt
Copy link
Author

I was able to resolve the issue with the following entries in Cargo.toml:

[package.metadata.raze.binary_deps]
refinery_cli = { version = "0.5.0", features = ["postgresql"] }

[package.metadata.raze.crates.refinery_cli.'0.5.0']
extra_aliased_targets = [
    "cargo_bin_refinery"
]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant