-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add support for Cargo workspaces #30
Conversation
Adds a new config variable, `cargo_workspace_member`, which is the path relative to the `cargo_project_path` directory where the member crate is located.
Is there a way to test this? Maybe even within my travis setup? Would love some input here or in https://github.com/matthiasbeyer/imag/pull/871 ! 👍 |
@matthiasbeyer In the Gemfile, after the gem 'thermite', git: 'https://github.com/malept/thermite.git', branch: 'cargo-workspaces' Then, in any file where you call |
I guess I have to do it in another way, as you can see in https://github.com/matthiasbeyer/imag/pull/871/commits/98530f2dc555d85dd74b782b96421c4c99d97f4a , I do not have a Gemfile but rather a gemspec. I also call thermite from the workspace member, so would rather need to specify the workspace root, am I right? |
As of https://github.com/matthiasbeyer/imag/pull/871/commits/565cdb3f2dbad2d847d51a4db9feef8c608418b3 I get:
|
Oh, I forgot one part. |
Another try with https://github.com/matthiasbeyer/imag/pull/871/commits/e6cc09857ee866b4432b103593a6025006bd232f yields
which is also clearly not what I want... |
Oh, I think I have to specify |
Adds a new config variable,
cargo_workspace_member
, which is the path relative to thecargo_project_path
directory where the member crate is located.Fixes #29.
CC: @matthiasbeyer