You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a monorepo that has implemented Bzlmod with a few languages in it, but we do not yet have Rust - we have some tools in our toolchain however that is written in Rust (including our own tooling in separate repositories). These projects are however not always published crates (and for our own tooling, we want to support a local development flow), and they are not Bzlmod repositories.
What would be the easiest way for us to "import" these projects, have rules_rust build them (including all of their external crate dependencies) and expose the binary that is produced?
If they were published crates, it would be easy to use this pattern:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We have a monorepo that has implemented Bzlmod with a few languages in it, but we do not yet have Rust - we have some tools in our toolchain however that is written in Rust (including our own tooling in separate repositories). These projects are however not always published crates (and for our own tooling, we want to support a local development flow), and they are not Bzlmod repositories.
What would be the easiest way for us to "import" these projects, have rules_rust build them (including all of their external crate dependencies) and expose the binary that is produced?
If they were published crates, it would be easy to use this pattern:
But since the binaries are not published crates, I am unsure how to go about this.
Beta Was this translation helpful? Give feedback.
All reactions